CVE-2026-97468
Description
A flaw was found in Apache CXF. The Security Token Service (STS) and token validation components cache validated security tokens using a weak, non-cryptographic hash function and treat cache matches as proof of validity. A remote attacker can craft a security token that generates a hash collision with a cached entry, bypassing signature verification and credential checks. Consequently, an attacker can impersonate other users and acquire valid service tokens under their identity.
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.
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.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.4 | N/A | 9.1 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.