CVE-2026-22741 Static resource cache poisoning in Spring MVC and WebFlux

Low 3.1 Published Updated

Attackers can poison static resource caches in Spring MVC or WebFlux applications, causing denial of service for clients.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-22741?

CVE-2026-22741 is a low-severity denial of service vulnerability in Vmware Spring Framework, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

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

Weakness: CWE-524

Which versions are affected by CVE-2026-22741?

16 open source packages ship an affected version, including org.springframework:spring-webflux and org.springframework:spring-webmvc. It affects 1 product.

PackageAffectedFixed in
org.springframework:spring-webflux MavenAll versions to 5.3.47None
org.springframework:spring-webflux MavenAll versions to 5.3.47None
org.springframework:spring-webflux MavenFrom 6.1.0 to 6.1.26None
org.springframework:spring-webflux MavenFrom 6.1.0 to 6.1.26None
org.springframework:spring-webflux MavenFrom 6.2.06.2.18
org.springframework:spring-webflux MavenFrom 6.2.06.2.18
10 more packages
org.springframework:spring-webflux MavenFrom 7.0.07.0.7
org.springframework:spring-webflux MavenFrom 7.0.07.0.7
org.springframework:spring-webmvc MavenAll versions to 5.3.47None
org.springframework:spring-webmvc MavenAll versions to 5.3.47None
org.springframework:spring-webmvc MavenFrom 6.1.0 to 6.1.26None
org.springframework:spring-webmvc MavenFrom 6.1.0 to 6.1.26None
org.springframework:spring-webmvc MavenFrom 6.2.06.2.18
org.springframework:spring-webmvc MavenFrom 6.2.06.2.18
org.springframework:spring-webmvc MavenFrom 7.0.07.0.7
org.springframework:spring-webmvc MavenFrom 7.0.07.0.7

Products include Vmware Spring Framework.

How do I fix CVE-2026-22741?

Upgrade org.springframework:spring-webflux to a fixed version for your release line: 6.2.18 or 7.0.7.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2026-22741 being exploited?

There is no known exploitation of CVE-2026-22741 in the wild and no public exploit code.

All Vmware Spring Framework vulnerabilities

Sources

Also known as CLEANSTART-2026-SB47522, CLEANSTART-2026-UZ00182, CLSA-2026-1779324468, DEBIAN-CVE-2026-22741, ECHO-6a71-dd8f-b1aa, GHSA-wg35-8jpf-2xv3 and 11 more.

Is CVE-2026-22741 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free