# CVE-2026-22740: Spring Framework DoS with Multipart Temp Files in WebFlux > Attackers can exhaust disk space by triggering multipart request processing in Spring WebFlux, leading to denial of service. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 29 Apr 2026 - **Updated:** 29 Apr 2026 - **Also known as:** CLEANSTART-2026-KE68240, CLEANSTART-2026-RE14874, CLSA-2026-1777509594, CLSA-2026-1777509595, CLSA-2026-1778460300, CLSA-2026-1779151614, CLSA-2026-1780361402, CLSA-2026-1781052747, CLSA-2026-1787120099, CLSA-2026-1790081647, CLSA-2026-1792601600, CLSA-2026-1792602671, CLSA-2026-1792606422, DEBIAN-CVE-2026-22740, ECHO-0adf-c3cd-ec6b, GHSA-5843-p793-ghmm, MINI-2q9r-64g2-3j77, MINI-58pw-xp2x-g32r, MINI-r9p7-h9jj-p664, MINI-xxg5-9h3h-8v3q, ROOT-APP-MAVEN-CVE-2026-22740, UBUNTU-CVE-2026-22740 ## What is CVE-2026-22740? CVE-2026-22740 is a medium-severity denial of service vulnerability in Vmware Spring Framework, published on 29 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A WebFlux server application that processes multipart requests creates temp files for parts larger than 10 K. Under some circumstances, temp files may remain not deleted after the request is fully processed. This allows an attacker to consume available disk space. Older, unsupported versions are also affected. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2026-22740? 8 open source packages ship an affected version, including org.springframework:spring-webflux. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework:spring-webflux` | Maven | All versions to 5.3.47 | None | | `org.springframework:spring-webflux` | Maven | All versions to 5.3.47 | None | | `org.springframework:spring-webflux` | Maven | From 6.1.0 to 6.1.26 | None | | `org.springframework:spring-webflux` | Maven | From 6.1.0 to 6.1.26 | None | | `org.springframework:spring-webflux` | Maven | From 6.2.0 | 6.2.18 | | `org.springframework:spring-webflux` | Maven | From 6.2.0 | 6.2.18 | | `org.springframework:spring-webflux` | Maven | From 7.0.0 | 7.0.7 | | `org.springframework:spring-webflux` | Maven | From 7.0.0 | 7.0.7 | Products: Vmware Spring Framework. ## How do I fix CVE-2026-22740? Upgrade org.springframework:spring-webflux to a fixed version for your release line: 6.2.18 or 7.0.7. ## Is CVE-2026-22740 being exploited? There is no known exploitation of CVE-2026-22740 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-47891](https://insights.sbomify.com/CVE-2026-47891/): Spring Framework maxInMemorySize Bypassed in Jaxb2Decoder (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) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-22740 and fix it if it is affected. What it is: CVE-2026-22740 is a medium-severity denial of service vulnerability in Vmware Spring Framework, published on 29 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-22740 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework:spring-webflux (Maven): affected all versions up to 5.3.47; no fix listed - org.springframework:spring-webflux (Maven): affected all versions up to 5.3.47; no fix listed - org.springframework:spring-webflux (Maven): affected from 6.1.0 up to 6.1.26; no fix listed - org.springframework:spring-webflux (Maven): affected from 6.1.0 up to 6.1.26; no fix listed - org.springframework:spring-webflux (Maven): affected from 6.2.0; fixed in 6.2.18 - org.springframework:spring-webflux (Maven): affected from 6.2.0; fixed in 6.2.18 - org.springframework:spring-webflux (Maven): affected from 7.0.0; fixed in 7.0.7 - org.springframework:spring-webflux (Maven): affected from 7.0.0; fixed in 7.0.7 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-22740/ (Markdown: https://insights.sbomify.com/CVE-2026-22740/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22740 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22740 - OSV: https://osv.dev/vulnerability/CVE-2026-22740 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-22740/ Summaries are generated and may contain mistakes; the official description above is the record.