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.
Update org.springframework:spring-webflux to 7.0.7; org.springframework:spring-webflux to 6.2.18; org.springframework:spring-webmvc to 7.0.7; org.springframework:spring-webmvc to 6.2.18 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSpring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources. affects org.springframework:spring-webflux (maven), org.springframework:spring-webflux (maven), org.springframework:spring-webflux (maven), org.springframework:spring-webflux (maven), org.springframework:spring-webmvc (maven), org.springframework:spring-webmvc (maven), org.springframework:spring-webmvc (maven), org.springframework:spring-webmvc (maven). Severity is low. 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.
AI coding agents often install or upgrade packages automatically in maven. A low vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
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.
Update org.springframework:spring-webflux to 7.0.7; org.springframework:spring-webflux to 6.2.18; org.springframework:spring-webmvc to 7.0.7; org.springframework:spring-webmvc to 6.2.18 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSpring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources. affects org.springframework:spring-webflux (maven), org.springframework:spring-webflux (maven), org.springframework:spring-webflux (maven), org.springframework:spring-webflux (maven), org.springframework:spring-webmvc (maven), org.springframework:spring-webmvc (maven), org.springframework:spring-webmvc (maven), org.springframework:spring-webmvc (maven). Severity is low. 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.
AI coding agents often install or upgrade packages automatically in maven. A low vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| org.springframework:spring-webfluxmaven | >=7.0.0,<=7.0.6 | 7.0.7 |
| org.springframework:spring-webfluxmaven | >=6.2.0,<=6.2.17 | 6.2.18 |
| org.springframework:spring-webfluxmaven | >=6.1.0,<=6.1.26 | Not reported |
| org.springframework:spring-webfluxmaven | <=5.3.47 | Not reported |
| org.springframework:spring-webmvcmaven | >=7.0.0,<=7.0.6 | 7.0.7 |
| org.springframework:spring-webmvcmaven | >=6.2.0,<=6.2.17 | 6.2.18 |
| org.springframework:spring-webmvcmaven | >=6.1.0,<=6.1.26 | Not reported |
| org.springframework:spring-webmvcmaven | <=5.3.47 | Not reported |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard| Package | Affected range | Fixed version |
|---|---|---|
| org.springframework:spring-webfluxmaven | >=7.0.0,<=7.0.6 | 7.0.7 |
| org.springframework:spring-webfluxmaven | >=6.2.0,<=6.2.17 | 6.2.18 |
| org.springframework:spring-webfluxmaven | >=6.1.0,<=6.1.26 | Not reported |
| org.springframework:spring-webfluxmaven | <=5.3.47 | Not reported |
| org.springframework:spring-webmvcmaven | >=7.0.0,<=7.0.6 | 7.0.7 |
| org.springframework:spring-webmvcmaven | >=6.2.0,<=6.2.17 | 6.2.18 |
| org.springframework:spring-webmvcmaven | >=6.1.0,<=6.1.26 | Not reported |
| org.springframework:spring-webmvcmaven | <=5.3.47 | Not reported |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard