Spring MVC applications using the functional web framework are vulnerable to stream corruption when using Server-Sent Events (SSE). Spring Framework 7.0.0 - 7.0.8 Spring Framework 6.2.0 - 6.2.19 Spring Framework 6.1.0 - 6.1.28 Spring Framework 6.0.0 - 6.0.30 Spring Framework 5.3.0 - 5.3.49
CVE-2026-59313
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-27. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 59(Track)EG Risk 59/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 computedSeverity98% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 32%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 28, 2026Server Sent Event stream corruption in Spring MVC functional web framework
https://spring.io/security/cve-2026-59313Vendor Advisories for CVE-2026-59313(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 19× in last 7d / 19× 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.
- 2026-08-30 02:59 UTCEG score recompute
- 2026-08-30 02:59 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 22:59 UTCGHSA enrichment
- 2026-08-29 18:58 UTCGHSA enrichment
- 2026-08-29 14:55 UTCGHSA enrichment
- 2026-08-29 10:55 UTCGHSA enrichment
- 2026-08-29 06:53 UTCGHSA enrichment
- 2026-08-29 02:52 UTCEG score recompute
- 2026-08-29 02:51 UTCGHSA enrichment
- 2026-08-28 22:50 UTCGHSA enrichment
- 2026-08-28 22:04 UTCEG score recompute▲ 9.80
- 2026-08-28 22:03 UTCGHSA enrichment
- 2026-08-28 21:59 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 18:59 UTCGHSA enrichment
- 2026-08-27 20:26 UTCNVD update
- 2026-08-27 20:16 UTCEG score recompute
- 2026-08-27 20:13 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-59313?
When was CVE-2026-59313 disclosed?
Is CVE-2026-59313 actively exploited?
What is the CVSS score of CVE-2026-59313?
How do I remediate CVE-2026-59313?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59313
Is Your Infrastructure Affected by CVE-2026-59313?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.