Apache WSS4J: WS-SecurityPolicy signature checks skipped in the streaming code after an STR-Transform reference (CVE-2026-92121) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-92121

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

Answer in brief

CVE-2026-92121 records a Unknown severity vulnerability in Apache WSS4J: WS-SecurityPolicy signature checks skipped in the streaming code after an STR-Transform reference. The current sources do not mark it as known exploited. The current feed maps Apache Software Foundation/org.apache.wss4j:wss4j-ws-security-stax (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 30, 2026Updated Sep 30, 2026Source checked Sep 30, 2026First seen by HOL Sep 30, 2026Material review Sep 30, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Apache Software Foundation/org.apache.wss4j:wss4j-ws-security-stax (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Apache Software Foundation/org.apache.wss4j:wss4j-ws-security-staxgeneric	>=4.0.0 <4.0.2 \|\| >=3.0.0 <3.0.6 \|\| >=0 <2.4.4	4.0.2, 3.0.6, 2.4.4

Recommended response

Check inventory. Check lockfiles and deployed manifests for Apache Software Foundation/org.apache.wss4j:wss4j-ws-security-stax.
Review the reported fix. Update Apache Software Foundation/org.apache.wss4j:wss4j-ws-security-stax to 4.0.2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 30, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.