Description
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.
Published: 2026-10-09
Score: 9.1 Critical
EPSS: < 1% Very Low
KEV: No
Impact: Authentication Bypass
Action: Apply Patch
AI Analysis

Impact

Apache CXF cached validated security tokens using Java Arrays.hashCode, a non‑cryptographic 32‑bit hash. When an attacker crafts a token that hashes to a value already in the cache, the library treats the cache hit as proof of prior validation, ignoring password verification, signature checking, and even calls to the STS. This permits the attacker to log in as any user and generate STS‑signed tokens for that identity, compromising confidentiality and integrity.

Affected Systems

The vulnerability affects the Apache Software Foundation’s Apache CXF product. All versions prior to 4.2.4, 4.1.9, and 3.6.13 are impacted, as those are the releases that contain the fixed implementation of the STS token validator and cache logic.

Risk and Exploitability

The CVE lacks an EPSS score and is not listed in the CISA KEV catalog, so publicly reported exploitation data is limited. Nevertheless, the weakness provides a direct authentication bypass that can be triggered remotely by submitting a forged token to any service that relies on CXF’s STS token validation. Given the ability to impersonate users and obtain privileged tokens, the risk level is high for affected installations. The CVSS score of 7.4 indicates a high severity impact.

Generated by OpenCVE AI on October 10, 2026 at 03:22 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor patch to upgrade Apache CXF to version 4.2.4, 4.1.9, or 3.6.13
  • If upgrading is temporarily infeasible, reconfigure CXF to disable or clear STS token caching so that each token is fully validated on receipt
  • Implement ongoing monitoring of authentication logs for anomalous or unexpected token usage and enforce strict credential policies

Generated by OpenCVE AI on October 10, 2026 at 03:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 20 Oct 2026 12:45:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:apache:cxf:*:*:*:*:*:*:*:*

Thu, 15 Oct 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}


Sun, 11 Oct 2026 12:45:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache cxf
Vendors & Products Apache
Apache cxf

Sat, 10 Oct 2026 02:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Sat, 10 Oct 2026 00:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-328
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}

threat_severity

Important


Fri, 09 Oct 2026 12:30:00 +0000

Type Values Removed Values Added
References

Fri, 09 Oct 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Fri, 09 Oct 2026 10:30:00 +0000

Type Values Removed Values Added
Description 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.
Title Apache CXF: Authentication bypass via weak cache keys for validated STS tokens
References

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-10-15T16:28:54.151Z

Reserved: 2026-09-24T15:28:31.804Z

Link: CVE-2026-97468

cve-icon Vulnrichment

Updated: 2026-10-09T11:08:02.810Z

cve-icon NVD

Status : Analyzed

Published: 2026-10-09T11:17:03.270

Modified: 2026-10-20T12:40:41.170

Link: CVE-2026-97468

cve-icon Redhat

Severity : Important

Publid Date: 2026-10-09T10:18:56Z

Links: CVE-2026-97468 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-11T12:27:36Z

Weaknesses