Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.
Published 29 Apr 2026 · Updated 10 Sept 2026
Is your project on an affected org.springframework:spring-webflux?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=7.0.0 <7.0.7
- Fixed in
- 7.0.7
mvn versions:use-dep-version -Dincludes=org.springframework:spring-webflux -DdepVersion=7.0.7 -DforceVersion=true- Affected
- >=6.2.0 <6.2.18
- Fixed in
- 6.2.18
mvn versions:use-dep-version -Dincludes=org.springframework:spring-webflux -DdepVersion=6.2.18 -DforceVersion=true- Affected
- >=6.1.0 <=6.1.26
- Fixed in
- No fix released
- Affected
- <=5.3.47
- Fixed in
- No fix released
- Affected
- >=7.0.0 <7.0.7
- Fixed in
- 7.0.7
mvn versions:use-dep-version -Dincludes=org.springframework:spring-webmvc -DdepVersion=7.0.7 -DforceVersion=true- Affected
- >=6.2.0 <6.2.18
- Fixed in
- 6.2.18
mvn versions:use-dep-version -Dincludes=org.springframework:spring-webmvc -DdepVersion=6.2.18 -DforceVersion=true- Affected
- >=6.1.0 <=6.1.26
- Fixed in
- No fix released
- Affected
- <=5.3.47
- Fixed in
- No fix released
Details
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.
Is GHSA-wg35-8jpf-2xv3 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.springframework:spring-webflux, and gives you the command that fixes it.
More advisories for org.springframework:spring-webflux
- CriticalCVE-2026-47892Spring Framework Header Predicate Bypass in WebFlux Functional Endpoints · 27 Aug 2026
- CriticalCVE-2026-47890Spring Framework Server Sent Event stream corruption while rendering fragments · 27 Aug 2026
- MediumCVE-2026-41853Spring Framework Multipart Request Smuggling in Spring MVC and WebFlux · 9 Jun 2026
- MediumCVE-2026-41847Spring Framework Security Filter Bypass in WebFlux Kotlin Router DSL · 9 Jun 2026
- HighCVE-2026-41842Spring Framework Denial of Service via Versioned Resources in Spring MVC and WebFlux · 9 Jun 2026
- MediumCVE-2026-41839Spring Framework Escalation via Session Fixation in WebFlux · 9 Jun 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.