Apache WSS4J replay checks bypassed by concurrent message copies
Original title: CVE-2026-115690: Apache WSS4J: Replay protection bypassed by concurrent copies of a message
Releases before 4.0.3, 3.0.7 and 2.4.5 record replay state only after validation, so concurrent copies can both pass.
Colm O hEigeartaigh reported CVE-2026-115690 in Apache WSS4J on November 16, rated moderate. WSS4J stores a UsernameToken nonce, a signed message's timestamp and signature, and a SAML 2.0 OneTimeUse assertion ID so a captured message is not accepted twice. It checked whether a value was already seen, validated the message, and only then continued the process described in the cut-off post. Affected ranges are 4.0.0 before 4.0.3, 3.0.0 before 3.0.7, and versions before 2.4.5.
Unconfirmed: The description is cut off after validation, so the exact recording step is not fully shown.
- Apache rates CVE-2026-115690 moderate.
- Affected code is 4.0.0 before 4.0.3 and 3.0.0 before 3.0.7.
- Releases before 2.4.5 are also affected.
- Tracked values include nonces, timestamps, signatures and OneTimeUse IDs.
- The seen-check occurs before validation finishes.
Impact: Replay protection bypassed by concurrent copies of a captured message
| Product | Affected | Fixed in |
|---|---|---|
| Apache WSS4J | 4.0.0 before 4.0.3; 3.0.0 before 3.0.7; before 2.4.5 | 4.0.3, 3.0.7, 2.4.5 |
- 1.Upgrade Apache WSS4J to 4.0.3, 3.0.7 or 2.4.5 for the installed line.
Vulnerabilities mentioned
All| CVE | Vulnerability | CVSS | EPSS | Signals | Published |
|---|---|---|---|---|---|
| CVE-2026-115690 | Race lets concurrent copies bypass Apache WSS4J replay cache | — | — |
From the original article
Posted by Colm O hEigeartaigh on Nov 16 Severity: moderate Affected versions: - Apache WSS4J 4. 0. 0 before 4.
seclists.org
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.