CVE-2026-92121 Affecting wss4j package, versions *
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-ECHOLATEST-WSS4J-20360994
- published1 Oct 2026
- disclosed30 Sept 2026
Introduced: 30 Sep 2026
NewCVE-2026-92121 (opens in a new tab)How to fix?
There is no fixed version for Echo:latest wss4j.
NVD Description
Note: Versions mentioned in the description apply only to the upstream wss4j package and not the wss4j package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
In the WSS4J streaming (StAX) code, a signature reference using the WS-Security STR-Transform leaves an internal "inside signed content" flag permanently set. The WS-SecurityPolicy enforcer uses that flag to decide whether an element needs checking, so it stops evaluating SignedParts and SignedElements for the rest of the message. A policy requiring the SOAP Body to be signed is then satisfied even when the Body carries no signature, removing the protection against XML Signature Wrapping. Signature verification itself is unaffected. The DOM code is not affected. Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4 which fix this issue.