CVE-2026-92121: Vulnerability in Apache Software Foundation Apache WSS4J
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.
AI Analysis
Technical Summary
In Apache 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 relies on this flag to decide if elements require checking, causing it to stop evaluating SignedParts and SignedElements for the remainder of the message. Consequently, a policy requiring the SOAP Body to be signed is erroneously satisfied even if the Body lacks a signature, effectively removing protection against XML Signature Wrapping attacks. Signature verification remains unaffected, and the DOM code is not vulnerable. Users are advised to upgrade to versions 4.0.2, 3.0.6, or 2.4.4 where this issue is fixed.
Potential Impact
The vulnerability allows bypassing WS-Security policy enforcement that requires the SOAP Body to be signed, potentially enabling XML Signature Wrapping attacks. This could lead to unauthorized message manipulation despite signature verification working correctly. The flaw affects only the streaming (StAX) code path, not the DOM code.
Mitigation Recommendations
Upgrade Apache WSS4J to version 4.0.2, 3.0.6, or 2.4.4 or later to remediate this vulnerability. No other mitigation is indicated or necessary as the issue is fixed in these versions.
CVE-2026-92121: Vulnerability in Apache Software Foundation Apache WSS4J
Description
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.
CVSS v3.1
Score 7.5high
Affected software
Apache Software Foundation
Apache WSS4J
pkg:maven/Apache Software Foundation/org.apache.wss4j:wss4j-ws-security-staxRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In Apache 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 relies on this flag to decide if elements require checking, causing it to stop evaluating SignedParts and SignedElements for the remainder of the message. Consequently, a policy requiring the SOAP Body to be signed is erroneously satisfied even if the Body lacks a signature, effectively removing protection against XML Signature Wrapping attacks. Signature verification remains unaffected, and the DOM code is not vulnerable. Users are advised to upgrade to versions 4.0.2, 3.0.6, or 2.4.4 where this issue is fixed.
Potential Impact
The vulnerability allows bypassing WS-Security policy enforcement that requires the SOAP Body to be signed, potentially enabling XML Signature Wrapping attacks. This could lead to unauthorized message manipulation despite signature verification working correctly. The flaw affects only the streaming (StAX) code path, not the DOM code.
Mitigation Recommendations
Upgrade Apache WSS4J to version 4.0.2, 3.0.6, or 2.4.4 or later to remediate this vulnerability. No other mitigation is indicated or necessary as the issue is fixed in these versions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-09-15T16:17:48.810Z
- State
- PUBLISHED
Threat ID: 6abd07622a4e24523d03fb2b
Added to database: 09/30/2026, 12:58:10 UTC
Last enriched: 09/30/2026, 13:03:18 UTC
Last updated: 10/01/2026, 03:24:26 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.