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.
CVE-2026-88021
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-10. a secondary CVSS source baseline 7.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(high)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 16%
- KEV
- Not listed
Published
September 10, 2026
Last Modified
September 10, 2026
Advisory Details (1)
Auto-updated Sep 10, 2026HCSEC-2026-37 - Consul vulnerable to an authorization bypass in the Connect service mesh - Security - HashiCorp Discuss
https://discuss.hashicorp.com/t/hcsec-2026-37-consul-vulnerable-to-an-authorization-bypass-in-the-connect-service-mesh/77739Vendor Advisories for CVE-2026-88021(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-11 19:08 UTCEG score recompute
- 2026-09-11 19:08 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 07:43 UTCEG score recompute
- 2026-09-11 07:43 UTCGHSA enrichment
- 2026-09-10 19:58 UTCEG score recompute▼ 0.40
- 2026-09-10 19:58 UTCNVD updateCVSS v3 → 7.1
- 2026-09-10 19:26 UTCEG score recompute▲ 0.40
- 2026-09-10 19:24 UTCMITRE cvelistV5CVSS v3 → 7.5
- 2026-09-10 19:18 UTCEG score recompute▼ 0.40
- 2026-09-10 19:18 UTCNVD updateCVSS v3 → 7.1
- 2026-09-10 19:10 UTCEG score recompute
- 2026-09-10 19:09 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-88021?
When was CVE-2026-88021 disclosed?
Is CVE-2026-88021 actively exploited?
What is the CVSS score of CVE-2026-88021?
How do I remediate CVE-2026-88021?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-88021
Is Your Infrastructure Affected by CVE-2026-88021?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.