Improper Verification of Cryptographic Signature Affecting org.apache.wss4j:wss4j-ws-security-policy-stax package, versions [,2.4.4)[3.0.0,3.0.6)[4.0.0,4.0.2)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGAPACHEWSS4J-21716533
- published26 Oct 2026
- disclosed30 Sept 2026
- creditReported by n0mi1k
Introduced: 30 Sep 2026
NewCVE-2026-87830 (opens in a new tab)How to fix?
Upgrade org.apache.wss4j:wss4j-ws-security-policy-stax to version 2.4.4, 3.0.6, 4.0.2 or higher.
Overview
Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature via XPath conversion in PolicyUtils and matching in SignedElementsAssertionState and related element assertion states in the StAX WS-SecurityPolicy validator. A remote SOAP peer can send a message containing an element covered by a relative or unsupported XPath expression; because the validator can convert the expression into a path that does not match the observed XML path, it may accept the message without enforcing the element’s required signature or encryption. This skips the policy check.