GitHub Advisoryadvisory · Maven
GHSA-8qq9-r6cc-qjv9 Spring Web Services: WSS4J validation does not use configured replay cache
LOW
Official page ↗
- Aliases
- CVE-2026-41000
- Ecosystem
- Maven
- Packages
- org.springframework.ws:spring-ws-security
- Severity
- Low
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
- Weaknesses
- CWE-294
- Reviewed
- 2026-08-21
Affected packages
• Maven org.springframework.ws:spring-ws-security: >= 5.0.0, < 5.0.2 → fixed in 5.0.2
• Maven org.springframework.ws:spring-ws-security: >= 4.1.0, < 4.1.4 → fixed in 4.1.4
• Maven org.springframework.ws:spring-ws-security: >= 4.0.0, <= 4.0.18 (no fix yet)
• Maven org.springframework.ws:spring-ws-security: >= 3.1.0, <= 3.1.8 (no fix yet)
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.
Related
Alias · CVE (1)
- CVE-2026-41000 Wss4jSecurityInterceptor did not consistently wire Apache WSS4J ReplayCache instances into RequestData for validation-time checks. vulnerability
Weakness · CWE (1)
- CWE-294 Authentication Bypass by Capture-replay weakness