Spring Security vulnerable to Authorization Bypass of Static Resources in WebFlux Applications (CVE-2024-38821)

Why this deserves its current priority

CVSS is 9.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps org.springframework.security:spring-security-web (maven), org.springframework.security:spring-security-web (maven), org.springframework.security:spring-security-web (maven), org.springframework.security:spring-security-web (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
org.springframework.security:spring-security-webmaven	>=5.8.0,<5.8.15	5.8.15
org.springframework.security:spring-security-webmaven	>=6.2.0,<6.2.7	6.2.7
org.springframework.security:spring-security-webmaven	>=6.0.0,<6.0.13	6.0.13
org.springframework.security:spring-security-webmaven	>=6.1.0,<6.1.11	6.1.11
org.springframework.security:spring-security-webmaven	>=6.3.0,<6.3.4	6.3.4
org.springframework.security:spring-security-webmaven	>=5.0.0,<5.7.13	5.7.13
org.springframework.security:spring-security-webmaven	>=5.0.0 <5.7.13	5.7.13
org.springframework.security:spring-security-webmaven	>=5.8.0 <5.8.15	5.8.15
org.springframework.security:spring-security-webmaven	>=6.2.0 <6.2.7	6.2.7
org.springframework.security:spring-security-webmaven	>=6.0.0 <6.0.13	6.0.13
org.springframework.security:spring-security-webmaven	>=6.1.0 <6.1.11	6.1.11
org.springframework.security:spring-security-webmaven	>=6.3.0 <6.3.4	6.3.4

Recommended response

Check inventory. Check lockfiles and deployed manifests for org.springframework.security:spring-security-web, org.springframework.security:spring-security-web, org.springframework.security:spring-security-web.
Review the reported fix. Update org.springframework.security:spring-security-web to 5.8.15; org.springframework.security:spring-security-web to 6.2.7; org.springframework.security:spring-security-web to 6.0.13; org.springframework.security:spring-security-web to 6.1.11; org.springframework.security:spring-security-web to 6.3.4; org.springframework.security:spring-security-web to 5.7.13; org.springframework.security:spring-security-web to 5.7.13; org.springframework.security:spring-security-web to 5.8.15; org.springframework.security:spring-security-web to 6.2.7; org.springframework.security:spring-security-web to 6.0.13; org.springframework.security:spring-security-web to 6.1.11; org.springframework.security:spring-security-web to 6.3.4 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 28, 2024
Evidence: source:ghsa:source_dates:source-dates:record
Source modified
Aug 31, 2026
Evidence: source:ghsa:source_dates:source-dates:record
First seen by HOL
Aug 31, 2026

Sources and claim methodology

Upstream source description

Spring WebFlux applications that have Spring Security authorization rules on static resources can be bypassed under certain circumstances. For this to impact an application, all of the following must be true: * It must be a WebFlux application * It must be using Spring's static resources support * It must have a non-permitAll authorization rule applied to the static resources support

Quoted source text, attributed separately from HOL analysis.