Wildfly: WSS4J EncryptedHeader child confusion could promote an attacker-controlled plaintext element as the decrypted
Affects wildflySource GCVE Database
Not known to be exploited · CVSS 9.1 Critical : upgrade to 39.0.1-r13 as a priority.
Data as of 20 Nov 2026, 03:33 UTC
- Patch
- Available – fixed in 39.0.1-r13
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 19 Nov 2026.
What to do
Upgrade wildfly to 39.0.1-r13.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
CleanStartwildflypkg:apk/cleanstart/wildfly?arch=aarch64Other threats | Affected
| Fixed in
|
CleanStartwildflypkg:apk/cleanstart/wildfly?arch=x86_64Other 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 Wildfly to version 39.0.1-r13 or later, where this vulnerability has been fixed. Since a patch is available, applying this official fix is the recommended remediation. No additional mitigations are indicated by the vendor advisory.
Description
A critical security vulnerability in Wildfly's WSS4J component allows an attacker to confuse EncryptedHeader child elements, promoting an attacker-controlled plaintext element as the decrypted header. This flaw can lead to incorrect confidentiality guarantees and potential policy bypass. The vulnerability affects Wildfly versions prior to 39.0.1-r13 and has a high CVSS score of 9.1. A patch is available in version 39.0.1-r13 to address this issue.