CVE-2026-89238: WSS4J EncryptedHeader child confusion could promote an attacker-controlled plaintext element as the decrypted
CVE-2026-89238 is a critical-severity flaw (CVSS 9.1) affecting wss4j. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
WSS4J EncryptedHeader child confusion could promote an attacker-controlled plaintext element as the decrypted header, leading to incorrect confidentiality coverage and possible policy bypass. Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4, which fix this issue.
Why this priority
- Critical severity
- Remotely exploitable, no login, no user action
- On your watchlist
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.1 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.3% (top 74%) |
| CISA exploited list | No |
| Weakness | CWE-345 |
| Published | 2026-09-30 |
| Last modified | 2026-10-06 |
Last updated 2026-10-06 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-89238?
wss4j: upgrade to 2.4.4, 3.0.6, 4.0.2. Exact commands for each OS are on this page.
Is CVE-2026-89238 being exploited?
CVE-2026-89238 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-89238 affect?
CVE-2026-89238 affects wss4j. Severity is critical (CVSS 9.1). WSS4J EncryptedHeader child confusion could promote an attacker-controlled plaintext element as the decrypted header, leading to incorrect confidentiality coverage and possible policy bypass. Users are recommended to upgrade to versions 4.0
How urgent is CVE-2026-89238?
Priority 48/100. Critical severity; Remotely exploitable, no login, no user action; On your watchlist
Related CVEs
- CVE-2026-87830 CRITICAL 9.1 UPGRADE In the StAX streaming WS-SecurityPolicy validator, certain relative or unsupported XPath expressions can be co
- CVE-2026-92121 HIGH 7.5 UPGRADE In the WSS4J streaming (StAX) code, a signature reference using the WS-Security STR-Transform leaves an intern
- CVE-2026-95616 HIGH 7.5 UPGRADE An integer overflow in WSS4J's DER bounds check lets an oversized allocation pass validation
- CVE-2026-92899 MEDIUM 4.8 UPGRADE Apache WSS4J remembers the Nonce of each UsernameToken it accepts, so a captured token cannot be reused
- CVE-2026-88920 CRITICAL 9.8 UPGRADE An authentication bypass in the DOM security processor in Apache WSS4J allows unauthenticated remote attackers