GHSA-m69x-pw9p-7j3q — spring-security-saml2-ser…
HIGHGHSA-m69x-pw9p-7j3q is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.springframework.security:spring-security-saml2-service-provider. A fix is available for org.springframework.security:spring-security-saml2-service-provider — see the affected versions and patch details below.
Spring Security SAML2 Service Provider: Unbounded writer inflates the compressed SAML payload into memory (DoS)
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-m69x-pw9p-7j3q.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-m69x-pw9p-7j3q by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.springframework.security:spring-security-saml2-service-provider☕org.springframework.security:spring-security-saml2-service-provider☕org.springframework.security:spring-security-saml2-service-provider☕org.springframework.security:spring-security-saml2-service-provider☕org.springframework.security:spring-security-saml2-service-provider☕org.springframework.security:spring-security-saml2-service-providerReal-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
An application using spring-security-saml2-service-provider and the REDIRECT binding for SAML 2.0 Login or Logout may be vulnerable to a denial of service by way of an unbounded writer that inflates the compressed SAML payload into memory.
Affected versions: Spring Security 5.7.0 through 5.7.23; 5.8.0 through 5.8.25; 6.3.0 through 6.3.16; 6.4.0 through 6.4.16; 6.5.0 through 6.5.10; 7.0.0 through 7.0.5.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.security:spring-security-saml2-service-provider | ≥ 7.0.0&&< 7.0.6 | 7.0.6org.springframework.security:spring-security-saml2-service-provider:7.0.6 |
| ☕Maven | org.springframework.security:spring-security-saml2-service-provider | ≥ 6.5.0&&< 6.5.11 | 6.5.11org.springframework.security:spring-security-saml2-service-provider:6.5.11 |
| ☕Maven | org.springframework.security:spring-security-saml2-service-provider | ≥ 6.4.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-saml2-service-provider | ≥ 6.3.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-saml2-service-provider | ≥ 5.8.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-saml2-service-provider | all versions | No fix |
Affected Products
spring securityvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-saml2-service-provider, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.security:spring-security-saml2-service-provider to 7.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m69x-pw9p-7j3q 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.
Frequently Asked Questions
Is GHSA-m69x-pw9p-7j3q in your dependencies?
Find it across Maven, including transitive dependencies.