CVE-2026-47891 Spring Framework maxInMemorySize Bypassed in Jaxb2Decoder
Attackers can cause denial of service in Spring WebFlux applications by bypassing memory limits during XML parsing.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-47891?
CVE-2026-47891 is a critical denial of service vulnerability in Vmware Spring Framework, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
A Spring WebFlux application that relies on the Aalto XML processor to parse XML input does not correctly enforce the maxInMemorySize limit. 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 Spring Framework 5.2.25.RELEASE and earlier
Weakness: CWE-770
Which versions are affected by CVE-2026-47891?
It affects 1 product.
Products include Vmware Spring Framework.
How do I fix CVE-2026-47891?
Upgrade to a fixed version.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2026-47891 being exploited?
There is no known exploitation of CVE-2026-47891 in the wild and no public exploit code.
Other vulnerabilities in Vmware Spring Framework
- CVE-2026-47884 Spring Framework Improper Path Limitation in XsltView
- CVE-2026-47890 Spring Framework Server Sent Event stream corruption while rendering fragments
- CVE-2026-47892 Spring Framework Header Predicate Bypass in WebFlux Functional Endpoints
- CVE-2026-59313 Server Sent Event stream corruption in Spring MVC functional web framework
- CVE-2016-1000027 Pivotal Spring Framework contains unsafe Java deserialization methods
Sources
Also known as CLEANSTART-2026-CF84062, CLEANSTART-2026-LS35751, CLEANSTART-2026-QW68592, DEBIAN-CVE-2026-47891, GHSA-7p67-m4j8-h4vx, UBUNTU-CVE-2026-47891.