# 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.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** CLEANSTART-2026-CF84062, CLEANSTART-2026-LS35751, CLEANSTART-2026-QW68592, DEBIAN-CVE-2026-47891, GHSA-7p67-m4j8-h4vx, UBUNTU-CVE-2026-47891

## 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 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-47891?

It affects 1 product.


Products: Vmware Spring Framework.

## How do I fix CVE-2026-47891?

Upgrade to a fixed version.

## 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](https://insights.sbomify.com/CVE-2026-47884/): Spring Framework Improper Path Limitation in XsltView (critical 9.8)
- [CVE-2026-47890](https://insights.sbomify.com/CVE-2026-47890/): Spring Framework Server Sent Event stream corruption while rendering fragments (critical 9.8)
- [CVE-2026-47892](https://insights.sbomify.com/CVE-2026-47892/): Spring Framework Header Predicate Bypass in WebFlux Functional Endpoints (critical 9.8)
- [CVE-2026-59313](https://insights.sbomify.com/CVE-2026-59313/): Server Sent Event stream corruption in Spring MVC functional web framework (critical 9.8)
- [CVE-2016-1000027](https://insights.sbomify.com/CVE-2016-1000027/): Pivotal Spring Framework contains unsafe Java deserialization methods (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47891 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-47891 in the wild and no public exploit code.

Affected product: Vmware Spring Framework. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47891/ (Markdown: https://insights.sbomify.com/CVE-2026-47891/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47891
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47891
- OSV: https://osv.dev/vulnerability/CVE-2026-47891

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47891/
Summaries are generated and may contain mistakes; the official description above is the record.