CVE-2026-92121: Apache WSS4J · CWE-693
Affects Apache WSS4JSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 4.0.2 : patch Apache WSS4J soon.
Data as of 14 Nov 2026, 20:44 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.0.2, 3.0.6, 2.4.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Sep 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 14 Nov 2026.
What to do
Upgrade Apache to 4.0.2, 3.0.6 or 2.4.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache WSS4J | Affected
| Fixed in
|
| Apache Software FoundationApache WSS4J | Affected
| Fixed in
|
| Apache Software FoundationApache WSS4J | Affected
| Fixed in
|
MavenApache Software Foundation/org.apache.wss4j:wss4j-ws-security-staxpkg:maven/Apache Software Foundation/org.apache.wss4j:wss4j-ws-security-staxOther 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 Apache WSS4J to versions 4.0.2, 3.0.6, or 2.4.4, which contain fixes for this vulnerability. No other mitigation is indicated by the vendor advisory.
Description
CVE-2026-92121 is a vulnerability in Apache WSS4J's streaming (StAX) code where a signature reference using the WS-Security STR-Transform causes an internal flag to remain set incorrectly. This leads the WS-SecurityPolicy enforcer to stop verifying signed parts for the remainder of the message, allowing a policy requiring the SOAP Body to be signed to be falsely satisfied even if the Body is unsigned. The DOM code is not affected. Versions 4.0.2, 3.0.6, and 2.4.4 include fixes for this issue.