Spring Security SAML2 Service Provider: Decryption Oracle Vulnerability from Unsigned SAML Response and Logout PayloadsGHSA-ww38-37g9-m3q3
LOWGHSA-ww38-37g9-m3q3 is a low-severity (CVSS 3.7) CWE-347 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.
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-ww38-37g9-m3q3.
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.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
Since Spring Security SAML decrypts SAML Responses as well as elements of SAML LogoutRequests and LogoutResponses without requiring a valid signature, attackers may be able to craft these SAML payloads and use the Service Provider as a decryption oracle.
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-ww38-37g9-m3q3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-ww38-37g9-m3q3 in your dependencies?
Find it across Maven, including transitive dependencies.