CVE-2026-87090

HIGHPre-NVD 8.38.3—
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

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 computed
Severity83% × 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, 2026
No patch confirmed yet.
generic

HCSEC-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/77736

Vendor 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 27× in last 7d / 37× 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.

  1. 2026-09-19 01:18 UTCEG score recompute
  2. 2026-09-19 01:18 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 13:42 UTCGHSA enrichment
  5. 2026-09-18 02:06 UTCEG score recompute
  6. 2026-09-18 02:06 UTCGHSA enrichment
  7. 2026-09-17 19:32 UTCEPSS rescore
  8. 2026-09-17 14:30 UTCGHSA enrichment
  9. 2026-09-17 02:53 UTCGHSA enrichment
  10. 2026-09-16 15:16 UTCEG score recompute
  11. 2026-09-16 15:16 UTCGHSA enrichment
  12. 2026-09-16 14:09 UTCEPSS rescore
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-16 03:40 UTCGHSA enrichment
  15. 2026-09-15 16:03 UTCGHSA enrichment
  16. 2026-09-15 04:27 UTCEG score recompute
  17. 2026-09-15 04:27 UTCGHSA enrichment
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-14 16:50 UTCGHSA enrichment
  21. 2026-09-14 05:14 UTCGHSA enrichment
  22. 2026-09-13 17:38 UTCEG score recompute
  23. 2026-09-13 17:38 UTCGHSA enrichment
  24. 2026-09-13 06:01 UTCGHSA enrichment
  25. 2026-09-12 18:25 UTCEG score recompute
Show 12 more
  1. 2026-09-12 18:25 UTCGHSA enrichment
  2. 2026-09-12 06:48 UTCGHSA enrichment
  3. 2026-09-11 19:11 UTCEG score recompute
  4. 2026-09-11 19:11 UTCGHSA enrichment
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 07:34 UTCEG score recompute
  8. 2026-09-11 07:34 UTCGHSA enrichment
  9. 2026-09-10 19:18 UTCEG score recompute
  10. 2026-09-10 19:10 UTCEG score recompute
  11. 2026-09-10 19:00 UTCEG score recompute
  12. 2026-09-10 18:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-87090?
CVE-2026-87090 is a high vulnerability published on September 10, 2026. 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…
When was CVE-2026-87090 disclosed?
CVE-2026-87090 was first published in the National Vulnerability Database on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-87090 actively exploited?
CVE-2026-87090 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.9% of all scored CVEs.
What is the CVSS score of CVE-2026-87090?
CVE-2026-87090 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-87090?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-87090, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-87090

Explore →

Is Your Infrastructure Affected by CVE-2026-87090?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs