Skip to content
VulniPulse
High7.5Apache Software Foundation

CVE-2026-92121: Apache 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 Apache advisory covers CVE-2026-92121. Related products: Apache WSS4J.

Open the Apache advisory

Key facts

Vendor rating
High, CVSS 7.5
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N · base score 7.5, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: high. Availability impact: none.
Weakness
  • CWE-693 Protection Mechanism Failure
EPSS
0.55% chance of exploitation in the next 30 days (46th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
CISA KEV
Not listed (catalogue checked )
Versions named
Apache WSS4J 4.0.0 before 4.0.2; Apache WSS4J 3.0.0 before 3.0.6; Apache WSS4J before 2.4.4
Fixed in
4.0.2, 3.0.6, 2.4.4
Source published
Source revised
Listed by VulniPulse

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Related products & platforms

Apache Software FoundationUnclassified

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.

Affected product named by the advisory: Apache WSS4J.

Text from the source record.

Versions named by the source
  • 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 ·verify at source

How to fix CVE-2026-92121

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

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

Apache Software Foundation advisories, September 2026All Apache Software Foundation advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache