CVE-2026-65583: CWE-345 Insufficient Verification of Data Authenticity in Apache Software Foundation Apache CXF
Apache CXF’s OIDC relying-party token validation could accept self-issued ID tokens without enforcing required claim checks (issuer/subject/audience/time and sub_jwk binding), enabling authentication bypass with crafted tokens. However, note that self-issued ID tokens are not accepted by default in the validator. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fixes this issue.
AI Analysis
Technical Summary
CVE-2026-65583 describes an insufficient verification of data authenticity (CWE-345) in Apache CXF's OpenID Connect (OIDC) relying-party token validation. The vulnerability arises because the validator could accept self-issued ID tokens without enforcing required claim checks including issuer, subject, audience, time validity, and sub_jwk binding. This weakness allows an attacker to bypass authentication by crafting tokens that exploit these missing checks. However, the default configuration does not accept self-issued ID tokens, which limits the risk unless explicitly enabled. The Apache Software Foundation recommends upgrading to Apache CXF versions 4.2.3, 4.1.8, or 3.6.12 where this issue is fixed.
Potential Impact
Successful exploitation of this vulnerability could allow an attacker to bypass authentication mechanisms relying on OIDC tokens in affected Apache CXF versions. This could lead to unauthorized access to protected resources or services that trust the token validation process. The impact is mitigated by the default rejection of self-issued tokens, but environments that enable acceptance of such tokens are at risk.
Mitigation Recommendations
Users should upgrade Apache CXF to version 4.2.3, 4.1.8, or 3.6.12 or later to remediate this vulnerability. Since the default validator configuration does not accept self-issued ID tokens, users who do not enable acceptance of these tokens are less exposed. Review and adjust token validation configurations to avoid accepting self-issued tokens unless necessary and ensure all required claim checks are enforced.
CVE-2026-65583: CWE-345 Insufficient Verification of Data Authenticity in Apache Software Foundation Apache CXF
Description
Apache CXF’s OIDC relying-party token validation could accept self-issued ID tokens without enforcing required claim checks (issuer/subject/audience/time and sub_jwk binding), enabling authentication bypass with crafted tokens. However, note that self-issued ID tokens are not accepted by default in the validator. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fixes this issue.
Affected software
pkg:maven/Apache Software Foundation/org.apache.cxf:cxf-rt-rs-security-sso-oidcRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-65583 describes an insufficient verification of data authenticity (CWE-345) in Apache CXF's OpenID Connect (OIDC) relying-party token validation. The vulnerability arises because the validator could accept self-issued ID tokens without enforcing required claim checks including issuer, subject, audience, time validity, and sub_jwk binding. This weakness allows an attacker to bypass authentication by crafting tokens that exploit these missing checks. However, the default configuration does not accept self-issued ID tokens, which limits the risk unless explicitly enabled. The Apache Software Foundation recommends upgrading to Apache CXF versions 4.2.3, 4.1.8, or 3.6.12 where this issue is fixed.
Potential Impact
Successful exploitation of this vulnerability could allow an attacker to bypass authentication mechanisms relying on OIDC tokens in affected Apache CXF versions. This could lead to unauthorized access to protected resources or services that trust the token validation process. The impact is mitigated by the default rejection of self-issued tokens, but environments that enable acceptance of such tokens are at risk.
Mitigation Recommendations
Users should upgrade Apache CXF to version 4.2.3, 4.1.8, or 3.6.12 or later to remediate this vulnerability. Since the default validator configuration does not accept self-issued ID tokens, users who do not enable acceptance of these tokens are less exposed. Review and adjust token validation configurations to avoid accepting self-issued tokens unless necessary and ensure all required claim checks are enforced.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-07-22T09:50:56.542Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a74768abf8831d539a9b736
Added to database: 08/06/2026, 11:56:58 UTC
Last enriched: 08/06/2026, 12:16:18 UTC
Last updated: 08/06/2026, 13:04:09 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.