CVE-2018-19653Medium· 5.9▾ SunlitHashiCorp Consul can use cleartext agent-to-agent RPC communication
▾ Sunlit zone — Low / medium · no exploitation signal
impact 32.5 · likelihood 0.2 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
1.2%
HashiCorp Consul 0.5.1 through 1.4.0 can use cleartext agent-to-agent RPC communication because the verify_outgoing setting is improperly documented. NOTE: the vendor has provided reconfiguration steps that do not require a software upgrade.
github.com/hashicorp/consul >= 0.5.1, < 1.4.1Upgrade to a patched release:
github.com/hashicorp/consul 1.4.1Connected by shared product, vendor, weakness, or advisory.
CVE-2025-11374Medium· 6.5Consul key/value endpoint is vulnerable to denial of service
CVE-2021-38698Medium· 6.5HashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint allowed services to register proxies for other services, enabling access…
CVE-2023-0845Medium· 6.5Consul Server Panic when Ingress and API Gateways Configured with Peering Connections
CVE-2021-41803High· 7.1HashiCorp Consul does not properly validate node or segment names prior to usage in JWT claim assertions
CVE-2023-3518High· 7.4Consul JWT Auth in L7 Intentions Allow for Mismatched Service Identity and JWT Providers
CVE-2020-7219High· 7.5Denial of Service (DoS) in HashiCorp Consul