Apache WSS4J Race Condition Allows Replay of OneTimeUse Assertions
Is it fixed? Not yet.
Ongoing since Nov 16, 10:16 UTC. First reported Nov 16, 10:16 UTC.
What happened
Apache WSS4J contains a vulnerability (CVE-2026-115690) where checking and remembering validation values (such as UsernameToken Nonces and SAML OneTimeUse assertions) occur as separate steps. If concurrent copies of the same message are processed simultaneously, they can all pass the check before any are recorded, allowing message replay.
What caused it?
The application checked whether a value had already been seen and validated the message as one step, and remembered the value in a separate subsequent step, creating a race condition when processing concurrent identical messages.
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on security advisory
Apache WSS4J remembers the UsernameToken Nonce, the Timestamp and signature of a signed message, and the ID of a SAML: CVE-2026-115690 (High)
Source
Evidence
1 report · 1 CVEShow
- [1]CVE First reportApache WSS4J remembers the UsernameToken Nonce, the Timestamp and signature of a signed message, and the ID of a SAML: CVE-2026-115690 (High)(opens security advisory in a new tab)
High severity. 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…
by Tenable 0upvotes 0comments
FAQ
What happened in the Apache issue?
Apache WSS4J contains a vulnerability (CVE-2026-115690) where checking and remembering validation values (such as UsernameToken Nonces and SAML OneTimeUse assertions) occur as separate steps. If concurrent copies of the same message are processed simultaneously, they can all pass the check before any are recorded, allowing message replay.
What is affected by the Apache issue?
Apache. Also affected at the same time: Linux.
When did the Apache issue start and end?
It started Nov 16, 10:16 UTC and is still ongoing (2 d 18 h so far). This page updates as it develops.
How do I get alerts for Apache?
Subscribe to the Apache RSS feed for every new Apache incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Apache is down. Apache feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.