CVE-2026-87830: Apache WSS4J · Expression Language Injection
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 12 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% 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 13 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-policy-staxpkg:maven/Apache Software Foundation/org.apache.wss4j:wss4j-ws-security-policy-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
Upgrade Apache WSS4J to version 4.0.2, 3.0.6, or 2.4.4 or later to remediate this vulnerability. No other mitigations are specified. Patch status is confirmed as fixed in these versions.
Description
CVE-2026-87830 is a critical vulnerability in Apache WSS4J's StAX streaming WS-SecurityPolicy validator. It allows certain relative or unsupported XPath expressions to bypass expected signature or encryption requirements in SOAP messages. This can lead to loss of confidentiality and integrity of these messages. The issue is fixed in versions 4.0.2, 3.0.6, and 2.4.4.