Answer in brief
CVE-2026-88021 records a Unknown severity vulnerability in Consul vulnerable to an authorization bypass in the Connect service mesh. The current sources do not mark it as known exploited. The current feed maps HashiCorp/Consul (generic), HashiCorp/Consul Enterprise (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps HashiCorp/Consul (generic), HashiCorp/Consul Enterprise (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| HashiCorp/Consulgeneric | >=1.9.0 <2.0.4 | 2.0.4 |
| HashiCorp/Consul Enterprisegeneric | >=1.9.0 <2.0.4 | 2.0.4 |
Published upstream
Sep 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.