CVE-2026-41000: CWE-294: Authentication Bypass by Capture-replay in Spring Spring Web Services
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.
AI Analysis
Technical Summary
The vulnerability arises because Wss4jSecurityInterceptor did not consistently integrate Apache WSS4J ReplayCache instances into RequestData during validation. As a result, replay protections configured by operators may not function correctly, allowing potential replay of authentication tokens and timestamps. This affects Spring Web Services versions 3.1.0 through 3.1.8, 4.0.0 through 4.0.18, 4.1.0 through 4.1.3, and 5.0.0 through 5.0.1. The CVSS v3.1 base score is 3.7, indicating a low severity vulnerability with network attack vector, high attack complexity, no privileges required, no user interaction, unchanged scope, no confidentiality or availability impact, and low integrity impact.
Potential Impact
The vulnerability can allow replay attacks that bypass authentication protections, potentially enabling attackers to reuse valid authentication tokens or timestamps. However, the impact is limited to low integrity loss without confidentiality or availability impact. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is indicated in the provided data. Operators should verify if updated versions or patches have been released by Spring to address this issue and apply them accordingly.
CVE-2026-41000: CWE-294: Authentication Bypass by Capture-replay in Spring Spring Web Services
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.
CVSS v3.1
Score 3.7low
Affected software
pkg:maven/org.springframework.ws/spring-ws-coreRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises because Wss4jSecurityInterceptor did not consistently integrate Apache WSS4J ReplayCache instances into RequestData during validation. As a result, replay protections configured by operators may not function correctly, allowing potential replay of authentication tokens and timestamps. This affects Spring Web Services versions 3.1.0 through 3.1.8, 4.0.0 through 4.0.18, 4.1.0 through 4.1.3, and 5.0.0 through 5.0.1. The CVSS v3.1 base score is 3.7, indicating a low severity vulnerability with network attack vector, high attack complexity, no privileges required, no user interaction, unchanged scope, no confidentiality or availability impact, and low integrity impact.
Potential Impact
The vulnerability can allow replay attacks that bypass authentication protections, potentially enabling attackers to reuse valid authentication tokens or timestamps. However, the impact is limited to low integrity loss without confidentiality or availability impact. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is indicated in the provided data. Operators should verify if updated versions or patches have been released by Spring to address this issue and apply them accordingly.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2026-04-16T02:19:12.970Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2a59be318757064921e1fa
Added to database: 6/11/2026, 6:46:22 AM
Last enriched: 6/11/2026, 7:01:45 AM
Last updated: 6/11/2026, 1:18:55 PM
Views: 16
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.