CVE-2026-57090

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.8%, top 47% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

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

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

Heap-based buffer overflow in Microsoft Windows Media Foundation allows an unauthorized attacker to execute code over a network.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity98% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 26, 2026

Advisory Details (1)

Auto-updated Jul 26, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-57090

Vendor Advisories for CVE-2026-57090(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 24× in last 7d / 48× 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-07-26 21:56 UTCVendor advisory
  2. 2026-07-26 21:56 UTCGHSA enrichment
  3. 2026-07-26 17:50 UTCVendor advisory
  4. 2026-07-26 17:50 UTCGHSA enrichment
  5. 2026-07-26 15:51 UTCEG score recompute
  6. 2026-07-26 15:51 UTCVendor advisory
  7. 2026-07-26 15:50 UTCGHSA enrichment
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-26 11:44 UTCEG score recompute
  11. 2026-07-26 11:44 UTCVendor advisory
  12. 2026-07-26 11:44 UTCGHSA enrichment
  13. 2026-07-26 04:44 UTCEG score recompute
  14. 2026-07-26 04:44 UTCVendor advisory
  15. 2026-07-26 04:43 UTCGHSA enrichment
  16. 2026-07-25 14:18 UTCEPSS rescore
  17. 2026-07-25 14:18 UTCEPSS rescore
  18. 2026-07-24 14:18 UTCEPSS rescore
  19. 2026-07-24 14:18 UTCEPSS rescore
  20. 2026-07-23 14:18 UTCEPSS rescore
  21. 2026-07-23 03:20 UTCEG score recompute
  22. 2026-07-22 14:08 UTCEPSS rescore
  23. 2026-07-21 15:25 UTCEPSS rescore
  24. 2026-07-20 17:08 UTCEPSS rescore
  25. 2026-07-19 14:31 UTCEPSS rescore
Show 23 more
  1. 2026-07-19 14:31 UTCEPSS rescore
  2. 2026-07-19 02:48 UTCEG score recompute▲ 1.00
  3. 2026-07-19 02:48 UTCVendor advisory
  4. 2026-07-19 02:48 UTCGHSA enrichment
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-17 16:00 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  8. 2026-07-17 06:42 UTCVendor advisory
  9. 2026-07-17 06:42 UTCGHSA enrichment
  10. 2026-07-16 18:31 UTCVendor advisory
  11. 2026-07-16 18:31 UTCGHSA enrichment
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-16 06:19 UTCVendor advisory
  14. 2026-07-16 06:19 UTCGHSA enrichment
  15. 2026-07-15 18:07 UTCVendor advisory
  16. 2026-07-15 18:06 UTCGHSA enrichment
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 16:57 UTCEPSS rescore
  19. 2026-07-15 05:54 UTCVendor advisory
  20. 2026-07-15 05:54 UTCGHSA enrichment
  21. 2026-07-14 17:42 UTCEG score recompute
  22. 2026-07-14 17:42 UTCVendor advisory
  23. 2026-07-14 17:40 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-57090?
CVE-2026-57090 is a critical vulnerability published on July 14, 2026. Heap-based buffer overflow in Microsoft Windows Media Foundation allows an unauthorized attacker to execute code over a network.
When was CVE-2026-57090 disclosed?
CVE-2026-57090 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57090 actively exploited?
CVE-2026-57090 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 46.8% of all scored CVEs.
What is the CVSS score of CVE-2026-57090?
CVE-2026-57090 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-57090?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57090, 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-57090

Explore →

Is Your Infrastructure Affected by CVE-2026-57090?

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

Start Free Scan →Browse All CVEs