Apache WSS4J remembers the UsernameToken Nonce, the Timestamp and signature of a signed message, and the ID of a SAML
Source GCVE Database
Not known to be exploited · fixed in 4.0.3 : patch Apache WSS4J soon.
Data as of 16 Nov 2026, 13:49 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
Users should upgrade to Apache WSS4J versions 4.0.3, 3.0.7, or 2.4.5, which include a fix that makes the replay cache check-and-remember operation atomic. Custom ReplayCache implementations should override the new ReplayCache.addIfAbsent method to ensure atomicity in their underlying storage. No other mitigation is indicated.
Description
Apache WSS4J had a vulnerability in its replay cache mechanism where it separately checked and then remembered values such as UsernameToken Nonce, Timestamp, signature, and SAML 2.0 OneTimeUse assertion IDs. This allowed an attacker who captured a valid message in transit to replay multiple copies simultaneously before any were recorded, causing the same authenticated request to be executed multiple times. The issue affects deployments using a replay cache, such as Apache CXF by default. The flaw is fixed by making the check-and-remember operation atomic. Upgrading to versions 4.0.3, 3.0.7, or 2.4.5 resolves the issue.