Quick answers
- Is CVE-2026-47891 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47891 being exploited in the wild.
- How severe is CVE-2026-47891?
- Critical severity, with a CVSS score of 9.8, published 27 August 2026.
- Which products and versions are affected?
- VMware Spring Framework 5.2.25 and earlier, 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-47891?
- 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-47891 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-47891?
- 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
The vulnerability is a resource exhaustion issue in Spring Framework's WebFlux module when using the Aalto XML processor for parsing XML input. The maxInMemorySize configuration parameter, which is intended to limit in-memory processing and prevent XML billion laughs or similar expansion attacks, is not correctly enforced. An attacker can send a specially crafted XML payload over the network to a vulnerable application without authentication, causing the parser to consume memory beyond the configured limit, leading to out-of-memory conditions and denial of service. The vulnerability affects Spring Framework versions 5.2.25 and earlier through 7.0.8.
Affected products
- VMware Spring Framework 5.2.25 and earlier, 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