~ / search / GHSA-wg35-8jpf-2xv3

GHSA-wg35-8jpf-2xv3

Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.

Source: GitHub Advisory Database (reviewed) Low CVE-2026-22741

Packages

EcosystemPackageAffectedFixed in
Maven org.springframework:spring-webflux >= 7.0.0, < 7.0.7 7.0.7
Maven org.springframework:spring-webflux >= 6.2.0, < 6.2.18 6.2.18
Maven org.springframework:spring-webflux >= 6.1.0, <= 6.1.26 no fix listed
Maven org.springframework:spring-webflux <= 5.3.47 no fix listed
Maven org.springframework:spring-webmvc >= 7.0.0, < 7.0.7 7.0.7
Maven org.springframework:spring-webmvc >= 6.2.0, < 6.2.18 6.2.18
Maven org.springframework:spring-webmvc >= 6.1.0, <= 6.1.26 no fix listed
Maven org.springframework:spring-webmvc <= 5.3.47 no fix listed

Details

As written in the advisory (Markdown source, shown as plain text).

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.

References

External links from the advisory. They lead to third-party sites.