Hashicorp Consul vulnerabilities
37 known vulnerabilities affecting hashicorp/consul.
Total CVEs
37
CISA KEV
0
Public exploits
2
Exploited in wild
1
Severity breakdown
CRITICAL1HIGH20MEDIUM16
Vulnerabilities
Page 2 of 2
CVE-2023-2816P3MEDIUMCVSS 6.5≥ 1.15.0, < 1.15.3v1.15.0+2 more2023-06-02
CVE-2023-2816 [MEDIUM] CWE-266 CVE-2023-2816: Consul and Consul Enterprise allowed any user with service:write permissions to use Envoy extensions
Consul and Consul Enterprise allowed any user with service:write permissions to use Envoy extensions configured via service-defaults to patch remote proxy instances that target the configured service, regardless of whether the user has permission to modify the service(s) corresponding to those modified proxies.
nvd
CVE-2025-11374P3MEDIUMCVSS 6.5fixed in 1.18.12fixed in 1.22.0+2 more2025-10-28
CVE-2025-11374 [MEDIUM] CWE-770 CVE-2025-11374: Consul and Consul Enterprise’s (“Consul”) key/value endpoint is vulnerable to denial of service (DoS
Consul and Consul Enterprise’s (“Consul”) key/value endpoint is vulnerable to denial of service (DoS) due to incorrect Content Length header validation. This vulnerability, CVE-2025-11374, is fixed in Consul Community Edition 1.22.0 and Consul Enterprise 1.22.0, 1.21.6, 1.20.8 and 1.18.12.
nvd
CVE-2025-11375P3MEDIUMCVSS 6.5fixed in 1.18.12fixed in 1.22.0+2 more2025-10-28
CVE-2025-11375 [MEDIUM] CWE-770 CVE-2025-11375: Consul and Consul Enterprise’s (“Consul”) event endpoint is vulnerable to denial of service (DoS) du
Consul and Consul Enterprise’s (“Consul”) event endpoint is vulnerable to denial of service (DoS) due to lack of maximum value on the Content Length header. This vulnerability, CVE-2025-11375, is fixed in Consul Community Edition 1.22.0 and Consul Enterprise 1.22.0, 1.21.6, 1.20.8 and 1.18.12.
nvd
CVE-2020-25201P3HIGHCVSS 7.5≥ 1.7.0, ≤ 1.8.42020-11-04
CVE-2020-25201 [HIGH] CVE-2020-25201: HashiCorp Consul Enterprise version 1.7.0 up to 1.8.4 includes a namespace replication bug which can
HashiCorp Consul Enterprise version 1.7.0 up to 1.8.4 includes a namespace replication bug which can be triggered to cause denial of service via infinite Raft writes. Fixed in 1.7.9 and 1.8.5.
nvdosv
CVE-2023-1297P3HIGHCVSS 7.5≥ 1.13.0, < 1.14.7≥ 1.15.0, < 1.15.3+2 more2023-06-02
CVE-2023-1297 [HIGH] CWE-826 CVE-2023-1297: Consul and Consul Enterprise's cluster peering implementation contained a flaw whereby a peer cluste
Consul and Consul Enterprise's cluster peering implementation contained a flaw whereby a peer cluster with service of the same name as a local service could corrupt Consul state, resulting in denial of service. This vulnerability was resolved in Consul 1.14.5, and 1.15.3
nvd
CVE-2021-38698P3MEDIUMCVSS 6.5fixed in 1.8.15≥ 1.9.0, < 1.9.9+1 more2021-09-07
CVE-2021-38698 [MEDIUM] CWE-862 CVE-2021-38698: HashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint allowed services to register proxie
HashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint allowed services to register proxies for other services, enabling access to service traffic. Fixed in 1.8.15, 1.9.9 and 1.10.2.
nvd
CVE-2019-9764P4HIGHCVSS 7.4v1.4.32019-03-26
CVE-2019-9764 [HIGH] CWE-346 CVE-2019-9764: HashiCorp Consul 1.4.3 lacks server hostname verification for agent-to-agent TLS communication. In o
HashiCorp Consul 1.4.3 lacks server hostname verification for agent-to-agent TLS communication. In other words, the product behaves as if verify_server_hostname were set to false, even when it is actually set to true. This is fixed in 1.4.4.
nvd
CVE-2021-41803P4HIGHCVSS 7.1≥ 1.8.1, < 1.11.9v1.12.4+1 more2022-09-23
CVE-2021-41803 [HIGH] CWE-862 CVE-2021-41803: HashiCorp Consul 1.8.1 up to 1.11.8, 1.12.4, and 1.13.1 do not properly validate the node or segment
HashiCorp Consul 1.8.1 up to 1.11.8, 1.12.4, and 1.13.1 do not properly validate the node or segment names prior to interpolation and usage in JWT claim assertions with the auto config RPC. Fixed in 1.11.9, 1.12.5, and 1.13.2."
nvd
CVE-2020-28053P4MEDIUMCVSS 6.5≥ 1.2.0, < 1.6.10≥ 1.7.0, < 1.7.10+1 more2020-11-23
CVE-2020-28053 [MEDIUM] CWE-863 CVE-2020-28053: HashiCorp Consul and Consul Enterprise 1.2.0 up to 1.8.5 allowed operators with operator:read ACL pe
HashiCorp Consul and Consul Enterprise 1.2.0 up to 1.8.5 allowed operators with operator:read ACL permissions to read the Connect CA private key configuration. Fixed in 1.6.10, 1.7.10, and 1.8.6.
nvdosv
CVE-2022-24687P4MEDIUMCVSS 6.5≥ 1.8.0, < 1.9.15≥ 1.10.0, < 1.10.8+1 more2022-02-24
CVE-2022-24687 [MEDIUM] CVE-2022-24687: HashiCorp Consul and Consul Enterprise 1.9.0 through 1.9.14, 1.10.7, and 1.11.2 clusters with at lea
HashiCorp Consul and Consul Enterprise 1.9.0 through 1.9.14, 1.10.7, and 1.11.2 clusters with at least one Ingress Gateway allow a user with service:write to register a specifically-defined service that can cause Consul servers to panic. Fixed in 1.9.15, 1.10.8, and 1.11.3.
nvd
CVE-2023-0845P4MEDIUMCVSS 6.5fixed in 1.14.5v1.14.0+4 more2023-03-09
CVE-2023-0845 [MEDIUM] CWE-476 CVE-2023-0845: Consul and Consul Enterprise allowed an authenticated user with service:write permissions to trigger
Consul and Consul Enterprise allowed an authenticated user with service:write permissions to trigger a workflow that causes Consul server and client agents to crash under certain circumstances. This vulnerability was fixed in Consul 1.14.5.
nvd
CVE-2024-10005P4MEDIUMCVSS 5.8≥ 1.4.1, < 1.20.1≥ 1.9.0, < 1.15.15+4 more2024-10-30
CVE-2024-10005 [MEDIUM] CWE-22 CVE-2024-10005: A vulnerability was identified in Consul and Consul Enterprise (“Consul”) such that using URL paths
A vulnerability was identified in Consul and Consul Enterprise (“Consul”) such that using URL paths in L7 traffic intentions could bypass HTTP request path-based access rules.
nvd
CVE-2024-10006P4MEDIUMCVSS 5.8≥ 1.4.1, < 1.20.1≥ 1.9.0, < 1.15.15+4 more2024-10-30
CVE-2024-10006 [MEDIUM] CWE-644 CVE-2024-10006: A vulnerability was identified in Consul and Consul Enterprise (“Consul”) such that using Headers in
A vulnerability was identified in Consul and Consul Enterprise (“Consul”) such that using Headers in L7 traffic intentions could bypass HTTP header based access rules.
nvd
CVE-2018-19653P4MEDIUMCVSS 5.9≥ 0.5.1, ≤ 1.4.02018-12-09
CVE-2018-19653 [MEDIUM] CWE-310 CVE-2018-19653: HashiCorp Consul 0.5.1 through 1.4.0 can use cleartext agent-to-agent RPC communication because the
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.
nvdosv
CVE-2020-12797P4MEDIUMCVSS 5.3≥ 1.4.0, < 1.6.6≥ 1.4.0, ≤ 1.6.6+1 more2020-06-11
CVE-2020-12797 [MEDIUM] CVE-2020-12797: HashiCorp Consul and Consul Enterprise failed to enforce changes to legacy ACL token rules due to no
HashiCorp Consul and Consul Enterprise failed to enforce changes to legacy ACL token rules due to non-propagation to secondary data centers. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4.
nvdosv
CVE-2024-10086P4MEDIUMCVSS 6.1≥ 1.4.1, < 1.15.15≥ 1.4.1, < 1.20.0+2 more2024-10-30
CVE-2024-10086 [MEDIUM] CWE-79 CVE-2024-10086: A vulnerability was identified in Consul and Consul Enterprise such that the server response did not
A vulnerability was identified in Consul and Consul Enterprise such that the server response did not explicitly set a Content-Type HTTP header, allowing user-provided inputs to be misinterpreted and lead to reflected XSS.
nvd
CVE-2020-7955P4MEDIUMCVSS 5.3≥ 1.4.1, < 1.6.22020-01-31
CVE-2020-7955 [MEDIUM] CWE-863 CVE-2020-7955: HashiCorp Consul and Consul Enterprise 1.4.1 through 1.6.2 did not uniformly enforce ACLs across all
HashiCorp Consul and Consul Enterprise 1.4.1 through 1.6.2 did not uniformly enforce ACLs across all API endpoints, resulting in potential unintended information disclosure. Fixed in 1.6.3.
nvdosv
← Previous2 / 2