GHSA-8qq9-r6cc-qjv9 — spring-ws-security
LOWGHSA-8qq9-r6cc-qjv9 is a low-severity (CVSS 3.7) CWE-294 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: WSS4J validation does not use configured replay cache
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-8qq9-r6cc-qjv9.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-8qq9-r6cc-qjv9 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 did not consistently wire Apache WSS4J ReplayCache instances into RequestData for validation-time checks. As a result, protections against replay of UsernameToken nonces and creation timestamps, Timestamp elements, and certain SAML one-time-use semantics could be ineffective even when operators configured a replay cache on the interceptor.
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-8qq9-r6cc-qjv9 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.
Red Hat rates this vulnerability as Low impact with a CVSS score of 3.7, consistent with the upstream assessment. Attack Complexity is High (AC:H) because the attacker must first capture a valid SOAP message in transit and then replay it within the token acceptance window, which defaults to 300 seconds. Impact is…
Ensure all SOAP endpoints using Spring Web Services WS-Security are accessed exclusively over TLS. This prevents attackers from capturing valid SOAP messages in transit, which is a prerequisite for exploiting the replay cache bypass. Additionally, reduce the WSS4J timestamp acceptance window (timeToLive) from the default 300 seconds to the minimum value the application can tolerate, limiting the replay window for any messages that may be intercepted through other means.Source: Red Hat security advisory for GHSA-8qq9-r6cc-qjv9 (CC BY 4.0)
Frequently Asked Questions
Is GHSA-8qq9-r6cc-qjv9 in your dependencies?
Find it across Maven, including transitive dependencies.