CVE-2026-90448

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.4%, top 74% 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 deployment mode intended to expose only read access to stored data proxies a set of application programming interface routes without restricting which request methods are allowed. One such route accepts a request that creates or overwrites a stored record, including an attacker-chosen identifier, using the application's own elevated backend credentials. This allows an authenticated user on a deployment intended to be read-only to forge or overwrite stored records that should not be modifiable in that deployment mode.

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
26%
KEV
Not listed

Published

September 11, 2026

Last Modified

September 18, 2026

References (1)

Vendor Advisories for CVE-2026-90448(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 28× in last 7d / 58× 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-25 04:23 UTCGHSA enrichment
  2. 2026-09-24 16:42 UTCEG score recompute
  3. 2026-09-24 16:42 UTCGHSA enrichment
  4. 2026-09-24 14:04 UTCEPSS rescore
  5. 2026-09-24 04:51 UTCEG score recompute
  6. 2026-09-24 04:51 UTCGHSA enrichment
  7. 2026-09-23 17:54 UTCEPSS rescore
  8. 2026-09-23 17:09 UTCGHSA enrichment
  9. 2026-09-23 05:25 UTCGHSA enrichment
  10. 2026-09-22 17:43 UTCEG score recompute
  11. 2026-09-22 17:43 UTCGHSA enrichment
  12. 2026-09-22 16:01 UTCEPSS rescore
  13. 2026-09-22 05:43 UTCEG score recompute
  14. 2026-09-22 05:43 UTCGHSA enrichment
  15. 2026-09-21 21:09 UTCEPSS rescore
  16. 2026-09-21 18:03 UTCGHSA enrichment
  17. 2026-09-21 06:21 UTCEG score recompute
  18. 2026-09-21 06:21 UTCGHSA enrichment
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-20 18:40 UTCGHSA enrichment
  21. 2026-09-20 06:59 UTCGHSA enrichment
  22. 2026-09-19 19:15 UTCEG score recompute
  23. 2026-09-19 19:15 UTCGHSA enrichment
  24. 2026-09-19 07:30 UTCGHSA enrichment
  25. 2026-09-18 19:48 UTCEG score recompute
Show 33 more
  1. 2026-09-18 19:48 UTCGHSA enrichment
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 18:59 UTCGHSA enrichment
  4. 2026-09-18 07:18 UTCGHSA enrichment
  5. 2026-09-17 19:37 UTCEG score recompute
  6. 2026-09-17 19:37 UTCGHSA enrichment
  7. 2026-09-17 19:32 UTCEPSS rescore
  8. 2026-09-17 05:43 UTCGHSA enrichment
  9. 2026-09-16 17:59 UTCEG score recompute
  10. 2026-09-16 17:59 UTCGHSA enrichment
  11. 2026-09-16 14:09 UTCEPSS rescore
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-16 04:36 UTCGHSA enrichment
  14. 2026-09-15 16:55 UTCGHSA enrichment
  15. 2026-09-15 05:14 UTCEG score recompute
  16. 2026-09-15 05:14 UTCGHSA enrichment
  17. 2026-09-15 03:12 UTCEPSS rescore
  18. 2026-09-14 17:28 UTCEG score recompute
  19. 2026-09-14 17:28 UTCGHSA enrichment
  20. 2026-09-14 16:20 UTCEG score recompute
  21. 2026-09-14 16:20 UTCGHSA enrichment
  22. 2026-09-14 08:52 UTCGHSA enrichment
  23. 2026-09-13 21:11 UTCEG score recompute
  24. 2026-09-13 21:11 UTCGHSA enrichment
  25. 2026-09-13 16:48 UTCEPSS rescore
  26. 2026-09-13 09:30 UTCGHSA enrichment
  27. 2026-09-12 21:49 UTCEG score recompute
  28. 2026-09-12 21:49 UTCGHSA enrichment
  29. 2026-09-12 15:02 UTCEPSS rescore
  30. 2026-09-12 10:08 UTCGHSA enrichment
  31. 2026-09-11 22:26 UTCEG score recompute
  32. 2026-09-11 21:54 UTCEG score recompute
  33. 2026-09-11 21:53 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-90448?
CVE-2026-90448 is a high vulnerability published on September 11, 2026. A deployment mode intended to expose only read access to stored data proxies a set of application programming interface routes without restricting which request methods are allowed. One such route accepts a request that creates or overwrites a stored record, including an attacker-chosen identifier,…
When was CVE-2026-90448 disclosed?
CVE-2026-90448 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-90448 actively exploited?
CVE-2026-90448 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 74.1% of all scored CVEs.
What is the CVSS score of CVE-2026-90448?
CVE-2026-90448 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-90448?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-90448, 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-90448

Explore →

Is Your Infrastructure Affected by CVE-2026-90448?

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

Book a Demo →Browse All CVEs