CVE-2026-59393: Memory Limit Bypass in Spring Framework WebFlux XML Decoding
CVE-2026-59393 is a memory consumption limit bypass in Spring Framework's WebFlux XML decoding with Jaxb2Decoder when using the Aalto XML parser. A specially crafted XML request or response body can cause decoding to exceed the configured maxInMemorySize limit, potentially resulting in denial of service. This vulnerability is a follow-up to CVE-2026-47891.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Processing specially crafted XML can consume memory beyond the application's configured maxInMemorySize limit, potentially exhausting available memory and causing denial of service.
Mitigation
If you can’t patch tonight, do this now.
No separate temporary workaround is specified. Upgrade to a corresponding fixed release; no additional mitigation steps are required after upgrading.
Remediation
Patch, then assume compromise.
Upgrade Spring Framework to the corresponding fixed release: 7.0.11 (OSS), or 7.0.10.1, 6.2.21, 6.1.30, 6.0.33, 5.3.51, or 5.2.27.RELEASE (Enterprise Support Only).
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-59393 exploited in the wild?
- As of Nov 20, 2026, Mallory has no reports of CVE-2026-59393 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-59393?
- As of Nov 20, 2026, Mallory has found no public exploit for CVE-2026-59393.
- Is there a patch for CVE-2026-59393?
- Upgrade Spring Framework to the corresponding fixed release: 7.0.11 (OSS), or 7.0.10.1, 6.2.21, 6.1.30, 6.0.33, 5.3.51, or 5.2.27.RELEASE (Enterprise Support Only).
Recent activity
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.