Skip to content
VulniPulse
Sign in
Advisory severityHigh7.5Apache Software Foundation

High [CVE-2026-92121] In the WSS4J streaming (StAX) code, a signature reference using the WS-Security STR-Transform leaves an internal "inside signed content" flag permanently set

This high-severity Apache Software Foundation advisory covers CVE-2026-92121; related products: Apache WSS4J.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-92121 Source published Source updated

VulniPulse record published Record updated

CVE-2026-92121
Related products & platforms
Apache Software FoundationUnclassified
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

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 product named by the advisory: Apache WSS4J.

Affected versions
  • Apache WSS4J 4.0.0 before 4.0.2
  • Apache WSS4J 3.0.0 before 3.0.6
  • Apache WSS4J before 2.4.4

Official advisory · high-confidence parse· fetched 6 days ago·verify at source

Fixed versions
  • 4.0.2
  • 3.0.6
  • 2.4.4

Official advisory · high-confidence parse· fetched 6 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4 which fix this issue.

Official advisory · high-confidence parse· fetched 6 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.