CVE-2026-115690: Apache WSS4J · Time-of-check Time-of-use (TOCTOU) Race Condition
Affects Apache WSS4JSource CVE Database V5
Not known to be exploited · fixed in 4.0.3 : patch Apache WSS4J soon.
Data as of 16 Nov 2026, 10:19 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 4.0.3, 3.0.7, 2.4.5
Exploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade Apache WSS4J and org/apache/wss4j to 4.0.3, 3.0.7 or 2.4.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache WSS4Jorg/apache:wss4j:wss4j-ws-security-common | Affected
| Fixed in
|
| Apache WSS4Jorg/apache:wss4j:wss4j-ws-security-common | Affected
| Fixed in
|
| Apache WSS4Jorg/apache:wss4j:wss4j-ws-security-common | Affected
| Fixed in
|
Mavenorg/apache/wss4jpkg:maven/org/apache/wss4jOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Apache WSS4J to version 4.0.3, 3.0.7, or 2.4.5 or later, where the replay cache check and remember operation is atomic, fixing the TOCTOU race condition. For custom ReplayCache implementations, override the new addIfAbsent method to ensure atomic operations in the underlying store. No other mitigation is indicated or necessary once patched.
Description
CVE-2026-115690 is a time-of-check to time-of-use (TOCTOU) race condition vulnerability in Apache WSS4J that affects replay cache handling. The flaw allows multiple copies of the same authenticated message to be accepted simultaneously if processed concurrently, enabling replay attacks. This occurs because the check for previously seen values and the remembering of those values were separate steps, not atomic. The issue affects deployments with a replay cache configured, such as Apache CXF by default. Fixed versions 4.0.3, 3.0.7, and 2.4.5 address this by making the check and remember operation atomic. Users should upgrade to these versions to mitigate the risk.