CVE-2025-11375

Consul and Consul Enterprise are vulnerable to an authorization bypass in the Connect service mesh. When building Envoy RBAC rules to enforce Connect intentions, Consul did not correctly escape certain characters in service names, namespaces, and partitions, causing the generated authorization rules to match more broadly than intended.

Consul and Consul Enterprise are vulnerable to an authorization bypass in the catalog deregistration path that may allow a local ACL token to delete peer-imported catalog objects. A caller with {{service:write}} or {{node:write}} permission may exploit this issue to remove services, checks, or nodes imported from a peered cluster without holding authority over the peer origin.

Consul and Consul Enterprise are vulnerable to a denial of service in the native RPC listener that may allow an authenticated client to exhaust server memory before ACL authorization is evaluated. A client that can complete the internal RPC mTLS handshake may exploit this issue without holding a valid ACL token.

Consul and Consul Enterprise are vulnerable to an authorization bypass in the catalog node-write path. An authenticated attacker with a token granting node-write permission on any single node name may delete another node's catalog registration and take over its node identity if they can obtain its node ID.

Consul Community Edition and Consul Enterprise versions 1.3.0 through 2.0.2 are vulnerable to an unauthenticated denial of service in several agent HTTP API endpoints. A remote caller could cause the agent to consume substantial memory before the request was rejected. This is fixed in Consul 2.0.3 and corresponding Enterprise versions.

Consul Community Edition and Consul Enterprise versions 1.18.21 through 2.0.2 are vulnerable to a partial arbitrary file read when configured to use the Vault Connect CA provider with JWT or AppRole authentication. A privileged attacker with `operator:write` permission may direct Consul to read and forward credential files outside the intended scope, potentially leading to exfiltration of sensitive secrets from the Consul server host.

Consul Community Edition and Consul Enterprise versions 1.19.1 through 2.0.2 did not enforce the `session:write` ACL permission for session deletion operations submitted through the transaction API. An authenticated caller with network access to the Consul server RPC port could delete arbitrary sessions without holding the required permission.

Consul Community Edition and Consul Enterprise versions 1.2.0 through 2.0.2 are vulnerable to an uncontrolled resource consumption issue in the Connect CA roots endpoint that may allow a remote caller to grow the agent's Connect CA roots cache without bound, defeating the operator's cache-disable configuration.

A vulnerability in Consul Community Edition and Consul Enterprise versions 1.17.0 through 2.0.2 causes uncontrolled resource consumption in the Connect authorization endpoint. This allows an attacker to grow the agent's intention-match cache without bound, defeating the operator's cache-disable configuration. The issue is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3.

A vulnerability in Consul Community Edition and Consul Enterprise versions 1.18.0 through 2.0.2 allows an authenticated attacker to crash the Consul server during the Enterprise-to-Community downgrade path. A caller with config-entry write permission can submit a service-router configuration entry that causes the agent to exit unexpectedly. The issue is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3.