CVE-2026-89238: Apache WSS4J · CWE-345
Affects Apache WSS4JSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical · fixed in 4.0.2 : patch Apache WSS4J as a priority.
Data as of 14 Nov 2026, 20:44 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% 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:H/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-dompkg:maven/Apache Software Foundation/org.apache.wss4j:wss4j-ws-security-domOther 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
A fix is available. Users should upgrade Apache WSS4J to version 4.0.2, 3.0.6, or 2.4.4 or later to remediate this vulnerability. Applying these official fixes will prevent exploitation of the EncryptedHeader child confusion issue.
Description
CVE-2026-89238 is a critical vulnerability in Apache WSS4J that allows an attacker to exploit EncryptedHeader child confusion. This flaw can cause an attacker-controlled plaintext element to be treated as the decrypted header, resulting in incorrect confidentiality coverage and potential policy bypass. The vulnerability affects multiple versions and has been fixed in Apache WSS4J versions 4.0.2, 3.0.6, and 2.4.4.