CVE-2026-97468

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.

Score

CVSS 3.1 9.1 Critical

Status

Analyzed - security@apache.org

Published

2026-10-09

Last modified

2026-10-20

Weaknesses

CWE-328

Affected products

• Cxf (Apache)
• Apache Cxf (Apache Software Foundation)

References

• https://lists.apache.org/thread.html/qthbnsyhqsxhl9p2h9v5dg4mnwv1b9r6
• http://www.openwall.com/lists/oss-security/2026/10/09/9