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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-22741 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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 |
Detection & 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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-22741 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-22741. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-22741 in your dependencies?
O3 Security finds CVE-2026-22741 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.