AI and data stack advisories

Severe, 6 weeks2431Projects328

2431 severe, 6 weeks · 328 projects

Apache WSS4J: race condition

Apache Software Foundation

CVE-2026-115690 · Published Nov 16, 2026 · updated Nov 20, 2026

High7.5
Fix: upgrade to 4.0.3 or later (3 fixed versions below)

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 versions

PackageAffectedFixed in
Apache WSS4J
Product
>= 4.0.0, < 4.0.34.0.3
>= 3.0.0, < 3.0.73.0.7
< 2.4.52.4.5
Details and references

More Apache Software Foundation advisories

All Apache Software Foundation