GHSA-x23c-287f-qqv5 CVE-2026-41842
Spring Framework Denial of Service via Versioned Resources in Spring MVC and WebFlux
High
Maven
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.40%
- Chance of exploitation in the next 30 days. Higher than 34.11% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
- Available
- 2 packages have a fixed version
Description
Spring MVC and WebFlux applications are vulnerable to Denial of Service (DoS) attacks when resolving static resources.
Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.0 through 5.3.48.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.springframework:spring-webflux | >= 7.0.0, < 7.0.8 |
7.0.8 |
| org.springframework:spring-webflux | >= 6.2.0, < 6.2.19 |
6.2.19 |
| org.springframework:spring-webflux | >= 6.1.0, <= 6.1.21 |
No fix yet |
| org.springframework:spring-webflux | <= 5.3.39 |
No fix yet |
| org.springframework:spring-webmvc | >= 7.0.0, < 7.0.8 |
7.0.8 |
| org.springframework:spring-webmvc | >= 6.2.0, < 6.2.19 |
6.2.19 |
| org.springframework:spring-webmvc | >= 6.1.0, <= 6.1.21 |
No fix yet |
| org.springframework:spring-webmvc | <= 5.3.39 |
No fix yet |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
org.springframework:spring-webflux Maven → 7.0.8
- maven
<dependency><groupId>org.springframework</groupId><artifactId>spring-webflux</artifactId><version>7.0.8</version></dependency>- gradle
implementation("org.springframework:spring-webflux:7.0.8")
org.springframework:spring-webmvc Maven → 7.0.8
- maven
<dependency><groupId>org.springframework</groupId><artifactId>spring-webmvc</artifactId><version>7.0.8</version></dependency>- gradle
implementation("org.springframework:spring-webmvc:7.0.8")
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Weakness
CWE-400: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How to prevent it
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-36p3-wjmg-h94x Remote Code Execution in Spring Framework | Critical Known exploited | Also affects org.springframework:spring-webflux |
| GHSA-9qf2-26p9-2q2q Spring Framework Header Predicate Bypass in WebFlux Functional Endpoints | Critical | Also affects org.springframework:spring-webflux |
| GHSA-j9f9-w8pj-32f8 Spring Framework Server Sent Event stream corruption while rendering fragments | Critical | Also affects org.springframework:spring-webflux |
| GHSA-pc63-qcmh-9cmg Spring Framework Improper Path Limitation in XsltView | Critical | Also affects org.springframework:spring-webmvc |
| GHSA-cjpg-rgq5-fr37 Spring Framework Multipart Request Smuggling in Spring MVC and WebFlux | Medium | Also affects org.springframework:spring-webflux |
| GHSA-vqgp-pf68-6947 Spring Framework Security Filter Bypass in WebFlux Kotlin Router DSL | Medium | Also affects org.springframework:spring-webflux |
| GHSA-957g-f97v-vppc Spring Framework Cross-site Scripting via JSP Form Tags | Medium | Also affects org.springframework:spring-webmvc |
| GHSA-3chg-m5w7-qfv5 Spring Framework Cross-site Scripting via JavaScriptUtils | Medium | Also affects org.springframework:spring-webmvc |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor