cve.bz

CVE-2026-88920 apache wss4j: Improper Authentication

9.8 criticalEPSS 0.6%

Critical (9.8) in apache wss4j. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
An authentication bypass in the DOM security processor in Apache WSS4J allows unauthenticated remote attackers to forge authenticated SOAP messages via a crafted unsigned SAML sender-vouches assertion containing an attacker-controlled key. 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

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 48th 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: total, 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-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
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-88920 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-88920?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-88920?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-88920 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-88920

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-88920](https://cve.bz/cve/badge/CVE-2026-88920.svg)](https://cve.bz/cve/CVE-2026-88920)

HTML:

<a href="https://cve.bz/cve/CVE-2026-88920"><img src="https://cve.bz/cve/badge/CVE-2026-88920.svg" alt="CVE-2026-88920"></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
Debian12, 13, 14wss4jno fix listedDEBIAN-CVE-2026-88920
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 2 morewss4jno fix listedUBUNTU-CVE-2026-88920

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.

Red Hat

Red Hat rates this Important.

Red Hat's statement

An authentication bypass flaw rated IMPORTANT by Red Hat affects the Apache WSS4J DOM security processor, which Red Hat ships in products including Red Hat JBoss EAP, Red Hat Single Sign-On 7.6, Red Hat JBoss Fuse 7, and the Red Hat build of Apache Camel. The vulnerability allows an unauthenticated remote attacker to bypass authentication and forge authenticated SOAP messages by submitting a crafted, unsigned SAML sender-vouches assertion containing an attacker-controlled key, enabling access to confidential data and unauthorized state-changing operations as the impersonated identity. Red Hat rated this flaw as IMPORTANT rather than the upstream CISA CRITICAL assessment (CVSS 9.8) because exploitation requires the affected service to be configured to process SAML sender-vouches assertions through the DOM security processor, a specialized, non-default WS-Security configuration. Fixes are being pursued for Red Hat JBoss EAP 8.1 and the Red Hat build of Apache Camel (Camel Quarkus 3 and Camel for Spring Boot 4.18). Red Hat JBoss EAP 7.4 and Red Hat Single Sign-On 7.6 also ship the vulnerable component, but no fix is planned for those product streams. Red Hat JBoss Fuse 7 is not affected because the vulnerable code is not in the execute path, and JBoss EAP XP 6 is not affected because the component is not present.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4 for Quarkus 3wss4j-ws-security-domAffected
Red Hat build of Apache Camel for Spring Boot 4wss4j-ws-security-domAffected
Red Hat Fuse 7wss4j-ws-security-domNot affected
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk11-openshift-rhel8Will not fix
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk17-openshift-rhel8Will not fix
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk8-openshift-rhel8Will not fix
Red Hat JBoss Enterprise Application Platform 7wss4j-ws-security-domWill not fix
Red Hat JBoss Enterprise Application Platform 8wss4j-ws-security-domAffected
Red Hat JBoss Enterprise Application Platform Expansion Packwss4j-ws-security-domNot affected
Red Hat Single Sign-On 7wss4j-ws-security-domWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-88920.

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON