Consul

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

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

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 bypass service mesh intentions. Fixed in 1.11.9, 1.12.5, and 1.13.2."

Published: 2022-09-23T00:00:00.000Z
Updated: 2025-05-27T14:54:21.059Z

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 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. Fixed in 1.9.17, 1.10.10, and 1.11.5.

Published: 2022-04-19T00:00:00.000Z
Updated: 2024-08-03T06:10:59.268Z

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.

Published: 2022-02-24T15:37:51.000Z
Updated: 2024-08-03T04:20:49.839Z

HashiCorp Consul Enterprise before 1.8.17, 1.9.x before 1.9.11, and 1.10.x before 1.10.4 has Incorrect Access Control. An ACL token (with the default operator:write permissions) in one namespace can be used for unintended privilege escalation in a different namespace.

Published: 2021-12-12T04:51:21.000Z
Updated: 2024-08-04T03:22:24.066Z

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."

Published: 2022-09-23T00:00:00.000Z
Updated: 2025-05-27T15:22:09.400Z

An issue was discovered in GoGo Protobuf before 1.3.2. plugin/unmarshal/unmarshal.go lacks certain index validation, aka the "skippy peanut butter" issue.

Published: 2021-01-11T05:57:18.000Z
Updated: 2024-08-03T16:45:51.251Z

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.

Published: 2021-09-07T11:45:14.000Z
Updated: 2024-08-04T01:51:19.213Z

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. Fixed in 1.8.15, 1.9.9 and 1.10.2.

Published: 2021-09-07T11:33:26.000Z
Updated: 2024-08-04T01:16:03.813Z

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 open, allowing L4 traffic. Fixed in 1.9.8 and 1.10.1.

Published: 2021-07-17T17:32:36.000Z
Updated: 2024-08-04T00:54:50.693Z

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. Fixed in 1.8.14, 1.9.8, and 1.10.1.

Published: 2021-07-17T17:28:11.000Z
Updated: 2024-08-03T23:25:30.307Z

HashiCorp Consul Enterprise version 1.8.0 up to 1.9.4 audit log can be bypassed by specifically crafted HTTP events. Fixed in 1.9.5, and 1.8.10.

Published: 2021-04-20T15:02:58.000Z
Updated: 2024-08-03T21:40:12.222Z

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 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.

Published: 2020-11-23T13:11:27.000Z
Updated: 2024-08-04T16:33:56.879Z

HashiCorp Consul and Consul Enterprise up to version 1.9.4 key-value (KV) raw mode was vulnerable to cross-site scripting. Fixed in 1.9.5, 1.8.10 and 1.7.14.

Published: 2021-04-20T13:07:21.000Z
Updated: 2024-08-04T15:49:05.907Z

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.

Published: 2020-11-04T22:32:10.000Z
Updated: 2024-08-04T15:33:05.268Z

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 (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 datacenters, because a token with literally "<hidden>" as its secret is used in unusual circumstances.

Published: 2019-03-05T23:00:00.000Z
Updated: 2024-08-04T21:17:31.211Z