NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

Resource Exhaustion in Spring SecurityGHSA-w9jg-gvgr-354m

HIGHFix: spring-projects/spring-security#9513

GHSA-w9jg-gvgr-354m is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.springframework.security:spring-security-core. A fix is available for org.springframework.security:spring-security-core — see the affected versions and patch details below.

Also known asCVE-2021-22119
Published
Updated
Affected
8 pkgs
Patched
8 / 8
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
6.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk
4.40%5.10%5.80%6.50%4.9%6.0%May 26Sep 26Nov 26

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

8 pkgs affected
☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-oauth2-client☕org.springframework.security:spring-security-oauth2-client☕org.springframework.security:spring-security-oauth2-client☕org.springframework.security:spring-security-oauth2-client

Real-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

Spring Security versions 5.5.x prior to 5.5.1, 5.4.x prior to 5.4.7, 5.3.x prior to 5.3.10 and 5.2.x prior to 5.2.11 are susceptible to a Denial-of-Service (DoS) attack via the initiation of the Authorization Request in an OAuth 2.0 Client Web and WebFlux application. A malicious user or attacker can send multiple requests initiating the Authorization Request for the Authorization Code Grant, which has the potential of exhausting system resources using a single session or multiple sessions.

Affected Packages

8 total 8 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.springframework.security:spring-security-core≥ 5.5.0&&< 5.5.15.5.1org.springframework.security:spring-security-core:5.5.1
☕Mavenorg.springframework.security:spring-security-core≥ 5.4.0&&< 5.4.75.4.7org.springframework.security:spring-security-core:5.4.7
☕Mavenorg.springframework.security:spring-security-core≥ 5.3.0&&< 5.3.105.3.10org.springframework.security:spring-security-core:5.3.10
☕Mavenorg.springframework.security:spring-security-core≥ 5.2.0&&< 5.2.115.2.11org.springframework.security:spring-security-core:5.2.11
☕Mavenorg.springframework.security:spring-security-oauth2-client≥ 5.5.0&&< 5.5.15.5.1org.springframework.security:spring-security-oauth2-client:5.5.1
☕Mavenorg.springframework.security:spring-security-oauth2-client≥ 5.4.0&&< 5.4.75.4.7org.springframework.security:spring-security-oauth2-client:5.4.7

Affected Products

2 products · 5 configurations
Application
communications cloud native core policyoracle
1 version
1.14.0
Application
spring securityvmware
≥ 5.5.0 && < 5.5.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.springframework.security:spring-security-core to 5.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w9jg-gvgr-354m is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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.

Red HatModerate
ProductFixed inAdvisory
Red Hat Fuse 7.11spring-security-oauth2-clientRHSA-2022:5532

Frequently Asked Questions

Spring Security versions 5.5.x prior to 5.5.1, 5.4.x prior to 5.4.7, 5.3.x prior to 5.3.10 and 5.2.x prior to 5.2.11 are susceptible to a Denial-of-Service (DoS) attack via the initiation of the Authorization Request in an OAuth 2.0 Client Web and WebFlux application. A malicious user or attacker can send multiple requests initiating the Authorization Request for the Authorization Code Grant, which has the potential of exhausting system resources using a single session or multiple sessions.
O3 Security · Impact-Aware SCA

Is GHSA-w9jg-gvgr-354m in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Resource Exhaustion in Spring Security (High 7.5)