Apache CXF 的 OIDC 依赖方组件在用户成功认证后,可能会将其重定向到由攻击者控制的 URL。该问题的原因在于,攻击者控制的 state 参数会被保留,并随后被用作重定向目标,但未验证最终解码后的 URI 是否属于信任提供方(RP)的域名。根据所使用的验证路径不同,直接编码或双重编码的外部 URL 均可触发此漏洞。建议用户升级到修复了该问题的版本,如 4.2.4、4.1.9 或 3.6.13。
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.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| Apache Software Foundation | Apache CXF | 4.2.0 ~ 4.2.4 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| 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-97468 | Apache CXF: Authentication bypass via weak cache keys for validated STS tokens | |
| CVE-2026-86463 | Apache CXF: FIQL Query Parser Denial of Service | |
| 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 |
No comments yet