{"id":"CVE-2026-97468","title":"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 to…","summary":"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 to…","severity":"none","published":"2026-10-09","updated":"2026-10-09","sourceUpdated":"2026-10-09T16:33:39.007","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-97468","references":[{"url":"https://lists.apache.org/thread.html/qthbnsyhqsxhl9p2h9v5dg4mnwv1b9r6","label":"security@apache.org"},{"url":"http://www.openwall.com/lists/oss-security/2026/10/09/9","label":"af854a3a-2127-422b-91ae-364da2661108"}],"tags":["nvd"],"ingestedAt":"2026-10-09T12:53:29.301Z","slug":"CVE-2026-97468","body":"## Overview\n\nApache 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.\nUsers are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}