CVE-2026-22741 — spring-webflux
LOWCVE-2026-22741 is a low-severity (CVSS 3.1) CWE-524 vulnerability in org.springframework:spring-webflux. A fix is available for org.springframework:spring-webflux — see the affected versions and patch details below.
Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-22741.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework:spring-webflux☕org.springframework:spring-webflux☕org.springframework:spring-webflux☕org.springframework:spring-webflux☕org.springframework:spring-webmvc☕org.springframework:spring-webmvc☕org.springframework:spring-webmvc☕org.springframework:spring-webmvcReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.
More precisely, an application can be vulnerable when all the following are true:
- the application is using Spring MVC or Spring WebFlux
- the application is configuring the resource chain support https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-config/static-resources.html#page-title with caching enabled
- the application adds support for encoded resources resolution
- the resource cache must be empty when the attacker has access to the application
When all the conditions above are met, the attacker can send malicious requests and poison the resource cache with resources using the wrong encoding. This can cause a denial of service by breaking the front-end application for clients.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework:spring-webflux | ≥ 7.0.0&&< 7.0.7 | 7.0.7org.springframework:spring-webflux:7.0.7 |
| ☕Maven | org.springframework:spring-webflux | ≥ 6.2.0&&< 6.2.18 | 6.2.18org.springframework:spring-webflux:6.2.18 |
| ☕Maven | org.springframework:spring-webflux | ≥ 6.1.0 | No fix |
| ☕Maven | org.springframework:spring-webflux | all versions | No fix |
| ☕Maven | org.springframework:spring-webmvc | ≥ 7.0.0&&< 7.0.7 | 7.0.7org.springframework:spring-webmvc:7.0.7 |
| ☕Maven | org.springframework:spring-webmvc | ≥ 6.2.0&&< 6.2.18 | 6.2.18org.springframework:spring-webmvc:6.2.18 |
Affected Products
spring frameworkvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-webflux, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework:spring-webflux to 7.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22741 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
To mitigate this issue, applications utilizing Spring MVC or Spring WebFlux should disable resource chain support caching or encoded resource resolution if these features are not essential for their operation. Consult Spring Framework documentation for specific configuration details. A restart of the affected application will be required for changes to take effect.Source: Red Hat security advisory for CVE-2026-22741 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-22741 in your dependencies?
Find it across Maven, including transitive dependencies.