CVE-2026-92121

published 30 Sep 2026 · updated 30 Sep 2026

Apache WSS4J: WS-SecurityPolicy signature checks skipped in the streaming code after an STR-Transform reference

7.5HighCVSS 7.5EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 2.4.4, 3.0.6 and 4.0.2.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Apache Software Foundation<2.4.4, >=3.0.0 <3.0.6, >=4.0.0 <4.0.22.4.4, 3.0.6, 4.0.2

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-92121 severity on Zeptric[![CVE-2026-92121](https://zeptric.io/badge/cve/CVE-2026-92121.svg)](https://zeptric.io/cve/CVE-2026-92121)