CVE-2026-115690
Published:November 16, 2026
Updated:November 16, 2026
Apache WSS4J remembers the UsernameToken Nonce, the Timestamp and signature of a signed message, and the ID of a SAML 2.0 "OneTimeUse" assertion, so that a captured message cannot be accepted twice. It checked whether a value had already been seen, validated the message, and only then remembered the value, as two separate steps. If several copies of the same message were processed at the same time, they could all pass the check before any of them was remembered, and all be accepted. An attacker who obtained a valid message before the recipient first processed it could send several copies at once, so that the same authenticated request was executed more than once. Where a UsernameToken is not bound to the message by a signature, the copies could carry different message bodies. The attacker needs to obtain the message while it is still in transit; a message captured after it has been accepted cannot be replayed. Affects deployments with a replay cache configured, as Apache CXF has by default. The value is now checked and remembered in a single atomic step. Custom ReplayCache implementations should override the new ReplayCache.addIfAbsent method with an operation that is atomic in their underlying store. Users are recommended to upgrade to versions 4.0.3 or 3.0.7 or 2.4.5, which fix this issue.
Affected Packages
https://github.com/apache/ws-wss4j.git (GITHUB):
Affected version(s) >=wss4j-4.0.0 <wss4j-4.0.3Fix Suggestion:
Update to version wss4j-4.0.3https://github.com/apache/ws-wss4j.git (GITHUB):
Affected version(s) >=wss4j-3.0.0 <wss4j-3.0.7Fix Suggestion:
Update to version wss4j-3.0.7https://github.com/apache/ws-wss4j.git (GITHUB):
Affected version(s) >=1_6_5 <wss4j-2.4.5 || >=wss4j-1.6.16 <wss4j-2.4.5 || =2_0-beta <wss4j-2.4.5 || >=wss4j-2.0.0-rc1 <wss4j-2.4.5Fix Suggestion:
Update to version wss4j-2.4.5org.apache.wss4j:wss4j-ws-security-stax (JAVA):
Affected version(s) >=2.0-beta <2.4.5Fix Suggestion:
Update to version 2.4.5org.apache.wss4j:wss4j-ws-security-stax (JAVA):
Affected version(s) >=4.0.0 <4.0.3Fix Suggestion:
Update to version 4.0.3org.apache.wss4j:wss4j-ws-security-stax (JAVA):
Affected version(s) >=3.0.0 <3.0.7Fix Suggestion:
Update to version 3.0.7org.apache.wss4j:wss4j-ws-security-dom (JAVA):
Affected version(s) >=3.0.0 <3.0.7Fix Suggestion:
Update to version 3.0.7org.apache.wss4j:wss4j-ws-security-dom (JAVA):
Affected version(s) >=2.0-beta <2.4.5Fix Suggestion:
Update to version 2.4.5org.apache.wss4j:wss4j-ws-security-dom (JAVA):
Affected version(s) >=4.0.0 <4.0.3Fix Suggestion:
Update to version 4.0.3Related Resources (2)
Do you need more information?
Contact UsCVSS v4
Base Score:
8.2
Attack Vector
NETWORK
Attack Complexity
HIGH
Attack Requirements
NONE
Privileges Required
NONE
User Interaction
NONE
Vulnerable System Confidentiality
NONE
Vulnerable System Integrity
HIGH
Vulnerable System Availability
NONE
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
5.9
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
NONE
Weakness Type (CWE)
Time-of-check Time-of-use (TOCTOU) Race Condition