Consul

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.

Published: 2026-03-11T23:08:32.414Z
Updated: 2026-04-17T17:57:55.646Z

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.

Published: 2025-10-28T20:12:14.325Z
Updated: 2025-12-09T01:37:57.188Z

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.

Published: 2025-10-28T20:19:05.292Z
Updated: 2026-04-17T18:34:14.829Z

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.

Published: 2024-10-30T21:21:46.559Z
Updated: 2025-01-10T13:06:42.658Z

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.

Published: 2024-10-30T21:20:37.011Z
Updated: 2025-01-10T13:06:41.296Z

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.

Published: 2024-10-30T21:19:22.576Z
Updated: 2025-01-10T13:06:39.935Z

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.

Published: 2023-08-09T15:06:52.406Z
Updated: 2024-10-08T14:56:28.934Z

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.

Published: 2023-06-02T22:43:34.553Z
Updated: 2024-10-07T20:12:01.627Z

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

Published: 2023-06-02T22:48:28.938Z
Updated: 2025-01-08T17:51:02.037Z

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.

Published: 2023-03-09T15:14:26.581Z
Updated: 2025-02-28T16:24:23.430Z

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.

Published: 2022-11-15T23:25:30.161Z
Updated: 2025-04-29T20:02:00.547Z

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.

Published: 2020-01-31T12:19:40.000Z
Updated: 2024-08-04T09:48:24.496Z

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. Fixed in 1.6.3.

Published: 2020-01-31T12:39:17.000Z
Updated: 2024-08-04T09:25:48.324Z

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. Fixed in 1.6.6 and 1.7.4.

Published: 2020-06-11T19:16:12.000Z
Updated: 2024-08-04T12:11:19.467Z

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. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4.

Published: 2020-06-11T19:41:25.000Z
Updated: 2024-08-04T12:11:19.316Z

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.

Published: 2020-06-11T19:37:19.000Z
Updated: 2024-08-04T12:04:22.912Z

HashiCorp Consul and Consul Enterprise could crash when configured with an abnormally-formed service-router entry. Introduced in 1.6.0, fixed in 1.6.6 and 1.7.4.

Published: 2020-06-11T19:23:26.000Z
Updated: 2024-08-04T12:04:22.893Z

HashiCorp Consul 1.4.0 through 1.5.0 has Incorrect Access Control. Keys not matching a specific ACL rule used for prefix matching in a policy can be deleted by a token using that policy even with default deny settings configured.

Published: 2019-06-06T16:35:38.000Z
Updated: 2024-08-04T23:17:39.422Z

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.

Published: 2018-12-09T19:00:00.000Z
Updated: 2024-08-05T11:44:20.263Z