Apache WSS4J Fixes Concurrent Replay of Authenticated Messages
Quick Answer
Upgrade WSS4J to 4.0.3, 3.0.7 or 2.4.5. Verify replay-cache atomicity, especially custom cache implementations and Apache CXF deployments.
Confirm Scope And Apply The Supported Remediation
What to do now: Find WSS4J versions in SOAP services, including transitive Apache CXF dependencies, and identify configured replay caches and backing stores. The attacker must obtain a valid message before the recipient first processes it. Review nonce, timestamp/signature and SAML OneTimeUse handling; a message captured after acceptance cannot be reused through this race. Deploy the fixed version for the release line. Implement ReplayCache.addIfAbsent atomically in any custom cache and its underlying store, following the project advisory. In an isolated test, submit simultaneous copies of a valid request and confirm that only one succeeds. Retain dependency resolution, cache implementation review and test evidence.
Last verified: 2026-11-16 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Apache WSS4J replay caches, including Apache CXF integrations |
|---|---|
| Advisory | CVE-2026-115690 |
| CVE | CVE-2026-115690 |
| Authoritative release date | 2026-11-16T09:48:39Z — original message timestamp from the official Apache mailing-list API. |
| Authority revision date | No separate material advisory revision is confirmed. |
| Affected versions | WSS4J 4.0.0 before 4.0.3; 3.0.0 before 3.0.7; and versions before 2.4.5, where a replay cache is configured. |
| Fixed version | Apache WSS4J 4.0.3, 3.0.7 or 2.4.5; custom ReplayCache implementations must provide an atomic addIfAbsent operation |
| CVSS base score | Not provided by the authority |
| CVSS severity | Moderate |
| Exploitation status | The cited Apache advisory does not confirm exploitation in the wild.; no exploitation claim is inferred. |
What Changed
The replay check and cache insertion were separate operations. Concurrent copies of an intercepted valid message could pass before any copy was recorded, allowing the same authenticated request to execute more than once.
What To Validate Now
- Inventory. Find WSS4J versions in SOAP services, including transitive Apache CXF dependencies, and identify configured replay caches and backing stores.
- Establish applicability. The attacker must obtain a valid message before the recipient first processes it. Review nonce, timestamp/signature and SAML OneTimeUse handling; a message captured after acceptance cannot be reused through this race.
- Remediate. Deploy the fixed version for the release line. Implement ReplayCache.addIfAbsent atomically in any custom cache and its underlying store, following the project advisory.
- Validate. In an isolated test, submit simultaneous copies of a valid request and confirm that only one succeeds. Retain dependency resolution, cache implementation review and test evidence.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
A routine package update alone may leave a custom non-atomic ReplayCache unsafe. Protect messages in transit and review duplicate side effects where warranted. The authority assigns Moderate severity but provides no CVSS base score.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.

