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.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://lists.apache.org/thread.html/qthbnsyhqsxhl9p2h9v5dg4mnwv1b9r6 Issue Tracking, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 5
- Cpes+1 CPE criteria (now 1)NVD modified 2026-10-20 12:40
- StatusUndergoing Analysis → AnalyzedNVD modified 2026-10-20 12:40
- CwesCWE-328NVD modified 2026-10-15 17:17
- CVSS9.1 (v3.1, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N)NVD modified 2026-10-15 17:17
- First seenunscoredNVD modified 2026-10-09 16:33
Affected (CPE criteria) 1
cpe:2.3:a:apache:cxf:*:*:*:*:*:*:*:*
References 2
- https://lists.apache.org/thread.html/qthbnsyhqsxhl9p2h9v5dg4mnwv1b9r6 Issue Tracking, Vendor Advisory
- http://www.openwall.com/lists/oss-security/2026/10/09/9 Mailing List, Third Party Advisory