CVE-2026-22741

published 29 Apr 2026 · updated 29 Apr 2026

Static resource cache poisoning in Spring MVC and WebFlux

3.1LowCVSS 3.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Spring Framework 5.3.48, Spring Framework 6.1.27, Spring Framework 6.2.18 and 1 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
VMwareSpring Framework>=5.3.0 <5.3.48, >=6.1.0 <6.1.27, >=6.2.0 <6.2.18, >=7.0.0 <7.0.75.3.48, 6.1.27, 6.2.18, 7.0.7

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Spring Framework, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-22741 severity on Zeptric[![CVE-2026-22741](https://zeptric.io/badge/cve/CVE-2026-22741.svg)](https://zeptric.io/cve/CVE-2026-22741)