9.8Critical
Vmware Spring Framework
CVE-2026-47891
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
What this means for your business
- It affects Vmware Spring Framework. It matters if your company, or a supplier that handles your data, runs it.
- An attacker can use it remotely, over a network, without a login, and without anyone at your company clicking anything.
- FIRST's prediction model gives it a 0.3% chance of attack attempts being seen in the next 30 days, ranking above 21% of all known flaws.
What to do
- 1Check whether your company or your suppliers run Vmware Spring Framework, and which version. The affected versions are listed further down this page.
- 2If you do, apply the vendor's fix. A patch or vendor advisory has been published.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
Scoring
- CVSS
- 9.8 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H- Weakness
- CWE-770
- Assigned by
- security@vmware.com
Dates
- Published
- 2026-08-27
- Last modified
- 2026-09-02
- Sources
- NVD
Affected products
- Vmware Spring Framework- 5.2.26, 5.3.0 - 5.3.50, 6.0.0 - 6.0.31, 6.1.0 - 6.1.29, 6.2.0 - 6.2.20, 7.0.0 - 7.0.8.1
As listed in the NVD configuration data. Not a statement about your estate.