Summary
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.
Impact
CVE-2026-22741 has a CVSS score of 3.1 (Low). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.0.7, 6.2.18); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
org.springframework:spring-webflux to 7.0.7 or later; org.springframework:spring-webflux to 6.2.18 or later; org.springframework:spring-webmvc to 7.0.7 or later; org.springframework:spring-webmvc to 6.2.18 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-22741? CVE-2026-22741 is a low-severity security vulnerability in org.springframework:spring-webflux (maven), affecting versions >= 7.0.0, <= 7.0.6. It is fixed in 7.0.7, 6.2.18.
- How severe is CVE-2026-22741? CVE-2026-22741 has a CVSS score of 3.1 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2026-22741?
org.springframework:spring-webflux(maven) (versions >= 7.0.0, <= 7.0.6)org.springframework:spring-webmvc(maven) (versions >= 7.0.0, <= 7.0.6)
- Is there a fix for CVE-2026-22741? Yes. CVE-2026-22741 is fixed in 7.0.7, 6.2.18. Upgrade to this version or later.
- Is CVE-2026-22741 exploitable, and should I be worried? Whether CVE-2026-22741 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-22741 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-22741?
- Upgrade
org.springframework:spring-webfluxto 7.0.7 or later - Upgrade
org.springframework:spring-webfluxto 6.2.18 or later - Upgrade
org.springframework:spring-webmvcto 7.0.7 or later - Upgrade
org.springframework:spring-webmvcto 6.2.18 or later
- Upgrade