CVE-2026-90447

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

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

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

A routing rule selects between two different authentication mechanisms for the same downstream service based on the value of a client-supplied request header, rather than on any property the client cannot control. An authenticated user in possession of a shared service credential can set this header to route around the primary role-based authorization check and reach the alternate path's fixed, elevated role instead. This allows a low-privileged authenticated attacker who knows the shared credential to perform actions reserved for a higher-privileged role.

CVSS v3
7.1
EG Score
7.1(medium)
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 computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

September 11, 2026

Last Modified

September 18, 2026

References (1)

Vendor Advisories for CVE-2026-90447(1)

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 31× in last 7d / 38× 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 19:44 UTCEG score recompute
  2. 2026-09-19 19:44 UTCGHSA enrichment
  3. 2026-09-19 07:46 UTCGHSA enrichment
  4. 2026-09-18 19:48 UTCGHSA enrichment
  5. 2026-09-18 19:33 UTCEG score recompute
  6. 2026-09-18 19:33 UTCGHSA enrichment
  7. 2026-09-18 19:28 UTCEPSS rescore
  8. 2026-09-18 07:35 UTCGHSA enrichment
  9. 2026-09-17 19:37 UTCEG score recompute
  10. 2026-09-17 19:37 UTCGHSA enrichment
  11. 2026-09-17 19:32 UTCEPSS rescore
  12. 2026-09-17 05:58 UTCGHSA enrichment
  13. 2026-09-16 17:59 UTCEG score recompute
  14. 2026-09-16 17:59 UTCGHSA enrichment
  15. 2026-09-16 14:09 UTCEPSS rescore
  16. 2026-09-16 05:23 UTCEG score recompute
  17. 2026-09-16 05:23 UTCGHSA enrichment
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-15 17:26 UTCGHSA enrichment
  20. 2026-09-15 05:29 UTCEG score recompute
  21. 2026-09-15 05:28 UTCGHSA enrichment
  22. 2026-09-15 03:12 UTCEPSS rescore
  23. 2026-09-14 17:28 UTCEG score recompute
  24. 2026-09-14 17:28 UTCGHSA enrichment
  25. 2026-09-14 16:20 UTCEG score recompute
Show 13 more
  1. 2026-09-14 16:20 UTCGHSA enrichment
  2. 2026-09-14 10:15 UTCGHSA enrichment
  3. 2026-09-13 22:18 UTCEG score recompute
  4. 2026-09-13 22:18 UTCGHSA enrichment
  5. 2026-09-13 16:48 UTCEPSS rescore
  6. 2026-09-13 10:20 UTCGHSA enrichment
  7. 2026-09-12 22:22 UTCEG score recompute
  8. 2026-09-12 22:22 UTCGHSA enrichment
  9. 2026-09-12 15:02 UTCEPSS rescore
  10. 2026-09-12 10:24 UTCGHSA enrichment
  11. 2026-09-11 22:26 UTCEG score recompute
  12. 2026-09-11 21:54 UTCEG score recompute
  13. 2026-09-11 21:53 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-90447?
CVE-2026-90447 is a high vulnerability published on September 11, 2026. A routing rule selects between two different authentication mechanisms for the same downstream service based on the value of a client-supplied request header, rather than on any property the client cannot control. An authenticated user in possession of a shared service credential can set this…
When was CVE-2026-90447 disclosed?
CVE-2026-90447 was first published in the National Vulnerability Database on September 11, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90447 actively exploited?
CVE-2026-90447 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 80.7% of all scored CVEs.
What is the CVSS score of CVE-2026-90447?
CVE-2026-90447 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-90447?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-90447, 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-90447

Explore →

Is Your Infrastructure Affected by CVE-2026-90447?

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

Start Free Scan →Browse All CVEs