CVE-2026-115690
7.5HighPublished 16 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User action
- None
- Impact
- High impact on integrity
- Weakness
- CWE-367
What an attacker gets
Remote attackers can replay captured messages to execute the same authenticated request multiple times. The attacker needs to intercept a valid message while it is in transit.
Root cause
The replay cache check and the subsequent storage of the message ID are performed as two separate, non-atomic steps.
Affected versions
Apache WSS4J versions prior to 4.0.3, 3.0.7, and 2.4.5.
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Fix & remediation
Upgrade to Apache WSS4J 4.0.3, 3.0.7, or 2.4.5. If using a custom ReplayCache implementation, override the addIfAbsent method to ensure atomic operations.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
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.