Hashicorp Consul Enterprise vulnerabilities

CVE-2026-2808 [MEDIUM] CWE-59 CVE-2026-2808: HashiCorp Consul and Consul Enterprise 1.18.20 up to 1.21.10 and 1.22.4 are vulnerable to arbitrary HashiCorp Consul and Consul Enterprise 1.18.20 up to 1.21.10 and 1.22.4 are vulnerable to arbitrary file read when configured with Kubernetes authentication. This vulnerability, CVE-2026-2808, is fixed in Consul 1.18.21, 1.21.11 and 1.22.5.

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.

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.

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.

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.

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.

CVE-2023-3518 [HIGH] CWE-266 CVE-2023-3518: HashiCorp Consul and Consul Enterprise 1.16.0 when using JWT Auth for service mesh incorrectly allow HashiCorp Consul and Consul Enterprise 1.16.0 when using JWT Auth for service mesh incorrectly allows/denies access regardless of service identities. Fixed in 1.16.1.

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

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.

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.

CVE-2022-3920 [HIGH] CWE-862 CVE-2022-3920: HashiCorp Consul and Consul Enterprise 1.13.0 up to 1.13.3 do not filter cluster filtering's importe 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. Fixed in 1.14.0.