Consul vulnerabilities
Consul is a service discovery that applications run on or next to (its releases): every project that runs it is exposed to its vulnerabilities, whatever its own code. Its advisories come from the NVD.
Recent advisories for Consul
-
High
CVSS 7.5
CVE-2019-12291: HashiCorp Consul 1.4.0 through 1.5.0 has Incorrect Access Control.
-
High
CVSS 8.1
CVE-2019-8336: HashiCorp Consul (and Consul Enterprise) 1.4.x before 1.4.3 allows a client to bypass intended access restrictions and obtain the privileges of one other arbitrary token within secondary...
-
High
CVSS 7.4
CVE-2019-9764: HashiCorp Consul 1.4.3 lacks server hostname verification for agent-to-agent TLS communication.
-
High
CVSS 7.5
CVE-2020-12758: HashiCorp Consul and Consul Enterprise could crash when configured with an abnormally-formed service-router entry.
-
High
CVSS 7.5
CVE-2020-13170: HashiCorp Consul and Consul Enterprise did not appropriately enforce scope for local tokens issued by a primary data center, where replication to a secondary data center was not enabled.
-
High
CVSS 7.5
CVE-2020-13250: HashiCorp Consul and Consul Enterprise include an HTTP API (introduced in 1.2.0) and DNS (introduced in 1.4.3) caching feature that was vulnerable to denial of service.
-
High
CVSS 7.5
CVE-2020-7219: HashiCorp Consul and Consul Enterprise up to 1.6.2 HTTP/RPC services allowed unbounded resource usage, and were susceptible to unauthenticated denial of service.
-
High
CVSS 8.6
CVE-2021-3121: An issue was discovered in GoGo Protobuf before 1.3.2.
-
High
CVSS 7.5
CVE-2021-32574: HashiCorp Consul and Consul Enterprise 1.3.0 through 1.10.0 Envoy proxy TLS configuration does not validate destination service identity in the encoded subject alternative name.
-
High
CVSS 7.5
CVE-2021-36213: HashiCorp Consul and Consul Enterprise 1.9.0 through 1.10.0 default deny policy with a single L7 application-aware intention deny action cancels out, causing the intention to incorrectly fail...
-
High
CVSS 8.8
CVE-2021-37219: HashiCorp Consul and Consul Enterprise 1.10.1 Raft RPC layer allows non-server agents with a valid certificate signed by the same CA to access server-only functionality, enabling privilege escalation.
-
High
CVSS 7.1
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 names prior to interpolation and usage in JWT claim assertions with the auto config RPC.
-
High
CVSS 7.5
CVE-2022-29153: HashiCorp Consul and Consul Enterprise up to 1.9.16, 1.10.9, and 1.11.4 may allow server side request forgery when the Consul client agent follows redirects returned by HTTP health check endpoints.
-
High
CVSS 7.5
CVE-2022-3920: HashiCorp Consul and Consul Enterprise 1.13.0 up to 1.13.3 do not filter cluster filtering's imported nodes and services for HTTP or RPC endpoints used by the UI.
-
High
CVSS 7.5
CVE-2023-1297: 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...
-
High
CVSS 7.3
CVE-2023-3518: HashiCorp Consul and Consul Enterprise 1.16.0 when using JWT Auth for service mesh incorrectly allows/denies access regardless of service identities.
-
High
CVSS 8.1
CVE-2023-5332: Patch in third party library Consul requires 'enable-script-checks' to be set to False.
-
Medium
CVSS 5.9
CVE-2018-19653: 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.
-
Medium
CVSS 5.3
CVE-2020-12797: HashiCorp Consul and Consul Enterprise failed to enforce changes to legacy ACL token rules due to non-propagation to secondary data centers.
-
Medium
CVSS 6.1
CVE-2020-25864: HashiCorp Consul and Consul Enterprise up to version 1.9.4 key-value (KV) raw mode was vulnerable to cross-site scripting.
-
Medium
CVSS 6.5
CVE-2020-28053: 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.
-
Medium
CVSS 5.3
CVE-2020-7955: 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.
-
Medium
CVSS 6.5
CVE-2021-38698: HashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint allowed services to register proxies for other services, enabling access to service traffic.
-
Medium
CVSS 6.5
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 least one Ingress Gateway allow a user with service:write to register a specifically-defined...
-
Medium
CVSS 6.5
CVE-2022-40716: HashiCorp Consul and Consul Enterprise up to 1.11.8, 1.12.4, and 1.13.1 do not check for multiple SAN URI values in a CSR on the internal RPC endpoint, enabling leverage of privileged access to...
-
Medium
CVSS 6.5
CVE-2023-0845: 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.
-
Medium
CVSS 6.5
CVE-2023-2816: 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...
-
Medium
CVSS 5.8
CVE-2024-10005: 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.
-
Medium
CVSS 5.8
CVE-2024-10006: 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.
-
Medium
CVSS 6.1
CVE-2024-10086: 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...
-
Medium
CVSS 6.5
CVE-2025-11374: Consul and Consul Enterprise’s (“Consul”) key/value endpoint is vulnerable to denial of service (DoS) due to incorrect Content Length header validation.
-
Medium
CVSS 6.5
CVE-2025-11375: 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.
Check your whole project
Consul is one package among hundreds in a lockfile. Upload your lockfile, or paste a public GitHub repository, and get every vulnerable package with the version that fixes it. Free, and no account needed.
About this data
Vulnerability data: the NVD. Licences: deps.dev. These pages list the versions AIssue checks every day for the projects it monitors, not every version ever released.