CVE-2026-115690 · Package
NO FIX YET · SEE WHAT TO DO
Apache WSS4J checked whether a message nonce, timestamp, signature or SAML OneTimeUse ID was already seen and remembered it in two separate steps, so concurrent copies of one message could all pass. An attacker who captures a message in transit can make the same authenticated request run more than once.
first public Nov 16, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Deployments that process WS-Security SOAP messages with a replay cache configured, which Apache CXF does by default. Attackers must capture a message while it is still in transit, before the recipient first processes it; messages already accepted cannot be replayed. Where a UsernameToken is not bound to the message by a signature, copies could also carry different bodies.
Not affected if message-already-processed, no-replay-cache, tls-protected-transport
Who cares apache-cxf, java, soap, web-services, wss4j
mvn dependency:tree output, looking for wss4j-ws-security-dom or wss4j-ws-security-common.ReplayCache implementation is in use.4.0.3, 3.0.7 or 2.4.5, which fix this issue.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.
This page as ·
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
ReplayCache implementations should override the new ReplayCache.addIfAbsent method with an operation that is atomic in their underlying store.NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.