cve.bz

CVE-2026-97468 apache cxf: Use of Weak Hash

9.1 criticalEPSS 0.2%

Critical (9.1) in apache cxf. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Apache CXF's STSTokenValidator and Security Token Service (STS) cached validated security tokens under a non-cryptographic 32-bit hash of the token (Java Arrays.hashCode/hashCode()), and treated a cache hit as proof that the presented token had already been validated. An attacker could craft a token (for example a UsernameToken or a self-signed SAML Assertion) whose hash collides with a cached entry. The token would then be accepted without password validation, signature trust verification or a call to the STS. This could let the attacker authenticate as another user and, through STS token validation or renewal, obtain STS-signed tokens for that identity. Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 13th 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-10-15. 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-328 Use of Weak Hash
OWASP Top 10
A04:2025 Cryptographic 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-97468 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97468?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97468?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-97468 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-97468

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

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache CXFfrom 4.2.0 before 4.2.4
Apache Software Foundation Apache CXFfrom 4.0.0 before 4.1.9
Apache Software Foundation Apache CXFbefore 3.6.13

Red Hat

Red Hat rates this Important.

Red Hat's statement

An authentication bypass flaw of Important severity (CVSS 7.4) was found in the Apache CXF STSTokenValidator and Security Token Service (STS) components as shipped in Red Hat middleware products, including Red Hat JBoss Fuse 7, JBoss EAP 8, and the Red Hat build of Apache Camel (both the Camel Quarkus and Camel for Spring Boot distributions). Apache CXF cached validated security tokens under a weak, non-cryptographic 32-bit hash (Java Arrays.hashCode/hashCode()) and treated a cache hit as proof that the presented token had already been validated. A remote, unauthenticated attacker could craft a security token, for example a UsernameToken or a self-signed SAML Assertion, whose hash collides with a cached entry; the crafted token would then be accepted without password validation, signature trust verification, or a call to the STS, letting the attacker authenticate as another user and, through STS token validation or renewal, obtain STS-signed tokens for that identity. The Red Hat severity (IMPORTANT, CVSS 7.4, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) is lower than the upstream CISA score (9.1, CRITICAL) because successful exploitation requires that a valid victim token is actively present in the cache and that the attacker craft a 32-bit hash collision against that entry within its lifetime, a condition the upstream rating does not account for. Fixes are being pursued for the affected products. JBoss EAP 7.4 contains the vulnerable component but its affected streams are out of support scope. EAP XP 6 was determined not affected because the vulnerable component is not present. For Red Hat Single Sign-On 7.6, the issue is tracked as delegated and a fix will not be pursued.

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. Upstream Apache CXF has addressed this issue in versions 4.2.4, 4.1.9, and 3.6.13; Red Hat customers should apply updated packages for their supported product streams when they become available.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4 for Quarkus 3cxf-rt-ws-securityAffected
Red Hat build of Apache Camel for Spring Boot 4cxf-rt-ws-securityAffected
Red Hat Fuse 7cxf-rt-ws-securityNot affected
Red Hat JBoss Enterprise Application Platform 7cxf-rt-ws-securityOut of support scope
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk11-openshift-rhel8Out of support scope
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk17-openshift-rhel8Out of support scope
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk8-openshift-rhel8Out of support scope
Red Hat JBoss Enterprise Application Platform 8cxf-rt-ws-securityAffected
Red Hat JBoss Enterprise Application Platform Expansion Packcxf-rt-ws-securityNot affected
Red Hat Single Sign-On 7cxf-rt-ws-securityWill 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-97468.

Attack patterns (CAPEC)

  • CAPEC-68 Subvert Code-signing Facilities Likelihood: Low · Severity: Very High
  • CAPEC-461 Web Services API Signature Forgery Leveraging Hash Function Extension Weakness Severity: High

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

References

Check your stackJSON