cve.bz

CVE-2026-92121 apache wss4j: Protection Mechanism Failure

7.5 highEPSS 0.5%

High (7.5) in apache wss4j. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-09-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-693 Protection Mechanism Failure
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-92121 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-92121?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-92121?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-92121 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-92121

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-92121](https://cve.bz/cve/badge/CVE-2026-92121.svg)](https://cve.bz/cve/CVE-2026-92121)

HTML:

<a href="https://cve.bz/cve/CVE-2026-92121"><img src="https://cve.bz/cve/badge/CVE-2026-92121.svg" alt="CVE-2026-92121"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache WSS4Jfrom 4.0.0 before 4.0.2
Apache Software Foundation Apache WSS4Jfrom 3.0.0 before 3.0.6
Apache Software Foundation Apache WSS4Jbefore 2.4.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13, 14wss4jno fix listedDEBIAN-CVE-2026-92121
Ubuntu20.04:LTS, 26.10wss4jno fix listedUBUNTU-CVE-2026-92121

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-693 (17).

References

Check your stackJSON