Skip to main content
No exploitation reportedFix available

CVE-2026-92121

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

No exploitation reported by the sources we read.

  • Published2026-09-30
  • Fixed in4.0.2 · 3.0.6 · 2.4.4
  • WeaknessCWE-693

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-09-3013:17CVE publishedNVD

Versions per branch

NVD
Apache wss4j
BranchAffectedFixed in
4.0≥ 4.0.0, < 4.0.24.0.2
3.0≥ 3.0.0, < 3.0.63.0.6
2.4< 2.4.42.4.4

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Apache Software Foundation Apache WSS4Jother versions: not affected

    package org.apache.wss4j:wss4j-ws-security-staxhttps://repo.maven.apache.org/maven2

    Affected
    • ≥ 4.0.0, < 4.0.2fixed in 4.0.2semver
    • ≥ 3.0.0, < 3.0.6fixed in 3.0.6semver
    • < 2.4.4fixed in 2.4.4semver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-09-30

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • org.apache.wss4j:wss4j-ws-security-staxRed Hat Lightwell:Mavenall versions · fixed in 4.0.1.rhlw-00003
  • wss4jUbuntu:26.10all versions · no fixed version listed
  • wss4jUbuntu:20.04:LTSall versions · no fixed version listed
  • wss4jDebian:14all versions · no fixed version listed
  • wss4jDebian:13all versions · no fixed version listed

Vendor advisories

  • CVE-2026-92121 Red Hat Product Security20 known affected

    wss4j: org.apache.wss4j/wss4j-ws-security-policy-stax: org.apache.wss4j/wss4j-ws-security-stax: org.apache.wss4j/wss4j: Apache WSS4J: Security policy bypass via STR-Transform reference

    wss4j-ws-security-policy-stax as a component of Red Hat build of Apache Camel 4 for Quarkus 3 · wss4j-ws-security-stax as a component of Red Hat build of Apache Camel 4 for Quarkus 3 · wss4j as a component of Red Hat build of Apache Camel for Spring Boot 4 · +17 more

Full record on NVD

Fix

  1. Update Apache wss4j to 4.0.2 · 3.0.6 · 2.4.4
  2. No fix available, says the vendor Red Hat Product Security CVE-2026-92121 · 9 productsFix deferred
  3. No fix planned, says the vendor Red Hat Product Security CVE-2026-92121 · 11 productsOut of support scope

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Published
2026-09-30
Last Modified
2026-10-06
NVD status
Analyzed
GitHub Advisory
GHSA-877v-57rx-34hv

Frequently asked questions

What is 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. 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.

Is CVE-2026-92121 actively exploited?

Active exploitation of CVE-2026-92121 has not been confirmed. Its EPSS score was 0.5% on 2026-11-16, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-92121?

CVE-2026-92121 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

Running wss4j? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record