Consul and Consul Enterprise are vulnerable to an authorization bypass in the catalog node-write path that may allow an authenticated attacker to delete another node's catalog registration and take over its node identity. An attacker with a token granting node-write permission on any single node name may exploit this issue if they can obtain the node ID of a node they do not control. This vulnerability (CVE-2026-87090) is fixed in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12 and 2.0.4.
CVE-2026-87090
Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-09-10. a secondary CVSS source baseline 8.3; 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
- 8.3
- EG Score
- 8.3(high)
- EG Risk
- 37(Track)EG Risk 37/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 computedSeverity83% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
September 10, 2026
Last Modified
September 10, 2026
Advisory Details (1)
Auto-updated Sep 10, 2026HCSEC-2026-34 - Consul vulnerable to an authorization bypass in the catalog node-write path - Security - HashiCorp Discuss
https://discuss.hashicorp.com/t/hcsec-2026-34-consul-vulnerable-to-an-authorization-bypass-in-the-catalog-node-write-path/77736Vendor Advisories for CVE-2026-87090(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 10× in last 7d / 10× 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:11 UTCEG score recompute
- 2026-09-11 19:11 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 07:34 UTCEG score recompute
- 2026-09-11 07:34 UTCGHSA enrichment
- 2026-09-10 19:18 UTCEG score recompute
- 2026-09-10 19:10 UTCEG score recompute
- 2026-09-10 19:00 UTCEG score recompute
- 2026-09-10 18:59 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-87090?
When was CVE-2026-87090 disclosed?
Is CVE-2026-87090 actively exploited?
What is the CVSS score of CVE-2026-87090?
How do I remediate CVE-2026-87090?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-87090
Is Your Infrastructure Affected by CVE-2026-87090?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.