Spring Framework server Web DoS VulnerabilityGHSA-r4q3-7g4q-x89m
HIGHGHSA-r4q3-7g4q-x89m is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.springframework:spring-core. A fix is available for org.springframework:spring-core — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-r4q3-7g4q-x89m.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework:spring-core☕org.springframework:spring-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
In Spring Framework versions 6.0.15 and 6.1.2, it is possible for a user to provide specially crafted HTTP requests that may cause a denial-of-service (DoS) condition.
Specifically, an application is vulnerable when all of the following are true:
- the application uses Spring MVC
- Spring Security 6.1.6+ or 6.2.1+ is on the classpath
Typically, Spring Boot applications need the org.springframework.boot:spring-boot-starter-web and org.springframework.boot:spring-boot-starter-security dependencies to meet all conditions.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework:spring-core | ≥ 6.1.2&&< 6.1.3 | 6.1.3org.springframework:spring-core:6.1.3 |
| ☕Maven | org.springframework:spring-core | ≥ 6.0.15&&< 6.0.16 | 6.0.16org.springframework:spring-core:6.0.16 |
Affected Products
spring frameworkvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework:spring-core to 6.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r4q3-7g4q-x89m is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
After careful consideration, Redhat has rated this vulnerability as moderate severity as successful exploitation of this flaw depends on various factors such as org.springframework.boot:spring-boot-starter-web and org.springframework.boot:spring-boot-starter-security dependencies, the application uses Spring…
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for GHSA-r4q3-7g4q-x89m (CC BY 4.0)
Frequently Asked Questions
Is GHSA-r4q3-7g4q-x89m in your dependencies?
Find it across Maven, including transitive dependencies.