CVE-2026-88021

Consul vulnerable to an authorization bypass in the Connect service mesh

Published Sep 10, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
Consul and Consul Enterprise are vulnerable to an authorization bypass in the Connect service mesh that may allow a service to reach a destination it is not authorized to access. 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. This vulnerability (CVE-2026-88021) is fixed in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12 and 2.0.4.

Analysis

AI-generated

Technical impact

Consul and Consul Enterprise allow a service to communicate with subjects it should not be allowed to reach due to inadequate escaping of service names, namespaces, and partitions when constructing Envoy RBAC rules for Connect intentions. The flaw enables an attacker who can influence the service mesh to have unauthorized access to service endpoints, potentially compromising confidentiality and availability of internal services.

Affected Systems

HashiCorp Consul and HashiCorp Consul Enterprise are affected. The vulnerability applies to all versions prior to Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12, and 2.0.4, which contain the fix. Users running any earlier releases should verify their version and consider upgrading.

Risk and Exploitability

The CVSS score of 7.5 indicates moderate to high risk. The EPSS score is not available, so the exploitation probability is uncertain, but the fact that the flaw enables bypass of the Connect service mesh suggests that an attacker with access to services in the cluster could abuse it. It is likely that the attack vector is internal or involves a compromised service, inferred from the required ability to generate or manipulate RBAC rules. The vulnerability is not listed in the CISA KEV catalog, but the impact to internal service communication warrants prioritization.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Consul 2.0.4 or newer, or to Consul Enterprise 1.21.18, 1.22.12, or 2.0.4 to apply the vendor‑provided fix.
  • Reduce the potential for this issue by sanitizing service names, namespaces, and partition identifiers to eliminate characters that could interfere with RBAC rule generation, and review any custom Connect intentions for proper escaping.
  • Implement monitoring or logging of unexpected or unauthorized service-to-service traffic within the mesh to detect potential abuse of the bypass mechanism.

Generated by OpenCVE AI on September 10, 2026 at 22:31 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Hashicorp
Hashicorp consul
Hashicorp consul Enterprise
Vendors & Products Hashicorp
Hashicorp consul
Hashicorp consul Enterprise
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Consul and Consul Enterprise are vulnerable to an authorization bypass in the Connect service mesh that may allow a service to reach a destination it is not authorized to access. 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. This vulnerability (CVE-2026-88021) is fixed in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12 and 2.0.4.
Title Consul vulnerable to an authorization bypass in the Connect service mesh
Weaknesses CWE-185
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N'}

Weaknesses
  • CWE-185

    Incorrect Regular Expression

Sources

Status
PUBLISHED
Assigner
HashiCorp
Published
Updated
Oct 2, 2026, 2:12 PM
Reserved
Sep 9, 2026, 7:40 PM
Status
Awaiting Analysis
Published
Sep 10, 2026, 7:17 PM
Modified
Sep 10, 2026, 8:17 PM