CVE-2026-69304

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory published 2026-09-08. the CNA's CVSS baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 3 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.9Exploit: None knownExposed: 0

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

Improper handling of highly compressed data (data amplification) in ASP.NET Core allows an unauthorized attacker to deny service over a network.

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

Published

September 8, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 8, 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-69304

Vendor Advisories for CVE-2026-69304(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 20× in last 7d / 40× 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-18 20:57 UTCEG score recompute
  2. 2026-09-18 20:57 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 14:05 UTCVendor advisory
  5. 2026-09-17 23:28 UTCVendor advisory
  6. 2026-09-17 20:07 UTCEG score recompute
  7. 2026-09-17 20:07 UTCVendor advisory
  8. 2026-09-16 22:08 UTCEG score recompute
  9. 2026-09-16 22:08 UTCVendor advisory
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-15 22:54 UTCVendor advisory
  13. 2026-09-15 17:50 UTCEG score recompute
  14. 2026-09-15 17:50 UTCVendor advisory
  15. 2026-09-14 23:06 UTCVendor advisory
  16. 2026-09-14 17:37 UTCVendor advisory
  17. 2026-09-13 23:27 UTCEG score recompute
  18. 2026-09-13 23:27 UTCVendor advisory
  19. 2026-09-12 23:01 UTCEG score recompute
  20. 2026-09-12 23:01 UTCVendor advisory
  21. 2026-09-11 22:35 UTCVendor advisory
  22. 2026-09-11 19:58 UTCVendor advisory
  23. 2026-09-11 16:58 UTCEG score recompute
  24. 2026-09-11 16:58 UTCVendor advisory
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 15 more
  1. 2026-09-11 09:37 UTCEPSS rescore
  2. 2026-09-10 22:14 UTCEG score recompute
  3. 2026-09-09 21:48 UTCVendor advisory
  4. 2026-09-09 20:00 UTCVendor advisory
  5. 2026-09-08 23:55 UTCEG score recompute
  6. 2026-09-08 23:55 UTCVendor advisory
  7. 2026-09-08 20:40 UTCEG score recompute
  8. 2026-09-08 20:40 UTCGHSA enrichment
  9. 2026-09-08 19:38 UTCGHSA enrichment
  10. 2026-09-08 18:39 UTCEG score recompute
  11. 2026-09-08 18:39 UTCVendor advisory
  12. 2026-09-08 18:39 UTCGHSA enrichment
  13. 2026-09-08 17:44 UTCEG score recompute
  14. 2026-09-08 17:44 UTCVendor advisory
  15. 2026-09-08 17:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-69304?
CVE-2026-69304 is a medium vulnerability published on September 8, 2026. Improper handling of highly compressed data (data amplification) in ASP.NET Core allows an unauthorized attacker to deny service over a network.
When was CVE-2026-69304 disclosed?
CVE-2026-69304 was first published in the National Vulnerability Database on September 8, 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-69304 actively exploited?
CVE-2026-69304 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.0% of all scored CVEs.
What is the CVSS score of CVE-2026-69304?
CVE-2026-69304 has a CVSS v4.0 base score of 5.9 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-69304?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69304, 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-69304

Explore →

Is Your Infrastructure Affected by CVE-2026-69304?

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

Start Free Scan →Browse All CVEs