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. This vulnerability (CVE-2026-87107) is fixed in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12 and 2.0.4.
CVE-2026-87107
Score 5.4 from GitHub Security Advisory published 2026-09-10. a secondary CVSS source baseline 5.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(high)
- EG Risk
- 24(Track)EG Risk 24/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 computedSeverity54% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
September 10, 2026
Last Modified
September 10, 2026
Advisory Details (1)
Auto-updated Sep 10, 2026HCSEC-2026-36 - Consul vulnerable to an authorization bypass in the catalog deregistration path - Security - HashiCorp Discuss
https://discuss.hashicorp.com/t/hcsec-2026-36-consul-vulnerable-to-an-authorization-bypass-in-the-catalog-deregistration-path/77738Vendor Advisories for CVE-2026-87107(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 9× in last 7d / 9× 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 18:36 UTCEG score recompute
- 2026-09-11 18:36 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 19:58 UTCEG score recompute
- 2026-09-10 19:25 UTCEG score recompute
- 2026-09-10 19:18 UTCEG score recompute
- 2026-09-10 19:10 UTCEG score recompute
- 2026-09-10 19:09 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-87107?
When was CVE-2026-87107 disclosed?
Is CVE-2026-87107 actively exploited?
What is the CVSS score of CVE-2026-87107?
How do I remediate CVE-2026-87107?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-87107
Is Your Infrastructure Affected by CVE-2026-87107?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.