CVE-2026-85532: Apache WSS4J · Improper Input Validation
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 13 Nov 2026, 23:54 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:N/A:HExploitation 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-commonpkg:maven/Apache Software Foundation/org.apache.wss4j:wss4j-ws-security-commonOther 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 to Apache WSS4J versions 4.0.2, 3.0.6, or 2.4.4 or later to address the improper input validation issue. No other mitigation is indicated by the vendor advisory.
Description
Apache WSS4J versions prior to 4.0.2, 3.0.6, and 2.4.4 improperly validate attacker-controlled derived-key lengths and offsets. This flaw allows the use of cryptographically weak keys or causes excessive CPU and memory consumption when processing crafted WS-Security messages. The issue is fixed by enforcing minimum and maximum key lengths and offset limits. Users should upgrade to fixed versions to mitigate the risk.