GHSA-gg9r-wr4p-w63h — spring-ws-security
HIGHGHSA-gg9r-wr4p-w63h is a high-severity (CVSS 8.2) CWE-1188 vulnerability in org.springframework.ws:spring-ws-security. A fix is available for org.springframework.ws:spring-ws-security — see the affected versions and patch details below.
Spring Web Services: Wss4jSecurityInterceptor disables WS-I BSP validation by default
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-gg9r-wr4p-w63h.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-gg9r-wr4p-w63h by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 382,795 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.ws:spring-ws-security☕org.springframework.ws:spring-ws-security☕org.springframework.ws:spring-ws-security☕org.springframework.ws:spring-ws-securityReal-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
Wss4jSecurityInterceptor initialized its BSP (WS-I Basic Security Profile) compliance flag so that inbound validation disabled WSS4J BSP enforcement on RequestData. Services that validate WS-Security on the network could therefore accept messages that violate BSP rules, weakening protocol-level checks.
Affected versions: Spring Web Services 5.0.0 through 5.0.1; 4.1.0 through 4.1.3; 4.0.0 through 4.0.18; 3.1.0 through 3.1.8.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.ws:spring-ws-security | ≥ 5.0.0&&< 5.0.2 | 5.0.2org.springframework.ws:spring-ws-security:5.0.2 |
| ☕Maven | org.springframework.ws:spring-ws-security | ≥ 4.1.0&&< 4.1.4 | 4.1.4org.springframework.ws:spring-ws-security:4.1.4 |
| ☕Maven | org.springframework.ws:spring-ws-security | ≥ 4.0.0 | No fix |
| ☕Maven | org.springframework.ws:spring-ws-security | ≥ 3.1.0 | No fix |
Affected Products
spring web servicesbroadcomDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.ws:spring-ws-security, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.ws:spring-ws-security to 5.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gg9r-wr4p-w63h 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.
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.
A flaw was found in Spring Web Services. The Wss4jSecurityInterceptor class incorrectly initializes its WS-I Basic Security Profile (BSP) compliance flag during inbound validation on RequestData, disabling BSP enforcement by default. A remote, unauthenticated attacker can exploit this behavior by sending non-compliant…
Explicitly enable WS-I Basic Security Profile compliance by invoking setBspCompliant(true) on configured Wss4jSecurityInterceptor bean instances during application initialization. Alternatively, configure custom inbound security handlers to enforce strict BSP validation rules at the application boundary.Source: Red Hat security advisory for GHSA-gg9r-wr4p-w63h (CC BY 4.0)
Frequently Asked Questions
Is GHSA-gg9r-wr4p-w63h in your dependencies?
Find it across Maven, including transitive dependencies.