Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-97468— Apache CXF: Authentication bypass via weak cache keys for validated STS tokens

Quick assessment

Affected
Apache Software Foundation Apache CXF
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Apache CXF 的 STS TokenValidator 和 Security Token Service (STS) 使用非密码学强度的 32 位哈希算法（即 Java 的 Arrays.hashCode() 或 hashCode()）对已验证的安全令牌进行缓存，并将缓存命中作为该令牌已通过验证的证明。攻击者可以构造一个哈希值与缓存条目发生碰撞的令牌（例如 UsernameToken 或自签名的 SAML 断言），从而绕过密码验证、签名信任验证以及向 STS 发起请求等正常验证流程，直接获得该令牌的接受。这

AI Predicted 8.1 Difficulty: Hard
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-97468

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Apache CXF: Authentication bypass via weak cache keys for validated STS tokens
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Apache Software Foundation Apache CXF 4.2.0 ~ 4.2.4 -

II. Public POCs for CVE-2026-97468

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-97468

请登录查看更多情报信息。

Other References for CVE-2026-97468 (1)

Same Patch Batch · Apache Software Foundation · 2026-10-09 · 13 CVEs total

CVE-2026-103413 8.8 HIGH Apache Camel Karavan: unvalidated Kubernetes resources applied from a project's kubernetes
CVE-2026-103412 8.8 HIGH Apache Camel Karavan: project file name path traversal when committing a project to Git
CVE-2026-108039 Apache CXF: Prevent unbounded XML document size in StaxUtils by adding default element and
CVE-2026-107938 Apache CXF: The Netty HTTP client transport does not perform TLS hostname verification.
CVE-2026-107937 Apache CXF: The attachment header size and count limits can be bypassed, which allows deni
CVE-2026-100227 Apache CXF: XML Signature wrapping in JAX-RS XML Security
CVE-2026-97791 Apache CXF: STSTokenValidator can accept untrusted SAML assertions because it shares valid
CVE-2026-86463 Apache CXF: FIQL Query Parser Denial of Service
CVE-2026-79650 Apache CXF: OIDC RP Open Redirect
CVE-2026-78384 Apache CXF: Unbounded DEFLATE Decompression in CXF JOSE/JWE and SAML Processing (Decompres
CVE-2026-73179 Apache CXF: JPA authorization-code consume is non-atomic
CVE-2026-71575 Apache CXF: Inoperative max_age authentication-freshness check in OidcClientCodeRequestFil

IV. Related Vulnerabilities

Same product: Apache CXF
Same vendor: Apache Software Foundation

V. Comments for CVE-2026-97468

No comments yet

Leave a comment