Quick answers
- Is CVE-2026-59313 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59313 being exploited in the wild.
- How severe is CVE-2026-59313?
- Critical severity, with a CVSS score of 9.8, published 27 August 2026.
- Which products and versions are affected?
- VMware Spring Framework 5.3.0-5.3.49, 6.0.0-6.0.30, 6.1.0-6.1.28, 6.2.0-6.2.19, 7.0.0-7.0.8.
- Is there a fix for CVE-2026-59313?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-59313 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-59313?
- Check whether you run VMware Spring Framework at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability affects Spring Framework's functional web framework implementation when handling Server-Sent Events (SSE). The root cause involves stream corruption when processing SSE responses, which can be triggered by a network-based attacker without authentication. The vulnerability impacts multiple versions across Spring Framework 5.3, 6.0, 6.1, 6.2, and 7.0 branches. An attacker can exploit this to corrupt or disrupt SSE streams, potentially leading to message loss or application-level denial of service for real-time communication features.
Affected products
- VMware Spring Framework 5.3.0-5.3.49, 6.0.0-6.0.30, 6.1.0-6.1.28, 6.2.0-6.2.19, 7.0.0-7.0.8
Timeline
- 2026-08-27: disclosed: CVE-2026-59313 published