CVE-2026-65583

Apache CXF: Self-issued ID token claims validation skipped

Published Aug 6, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Apache CXF’s OIDC relying‑party token validator allows self‑issued ID tokens to bypass required claim checks for issuer, subject, audience, time, and sub_jwk binding. This flaw means an attacker can craft a token that appears legitimate and gain authenticated access to the system without using a real identity. The weakness is classified as CWE‑345, a violation of the Authentication Expectation principle.

Affected Systems

The vulnerability affects Apache CXF releases prior to 4.2.3, 4.1.8, or 3.6.12. Any deployment using an older Apache CXF version that participates in OIDC authentication is potentially exposed unless it disables self‑issued token support.

Risk and Exploitability

The EPSS score is not available and the CVE is not listed in the CISA KEV catalog, but the nature of the flaw—an authentication bypass—raises high concern. An attacker who can issue or obtain a crafted ID token can impersonate any user and access protected resources. Based on the description, the likely attack vector is remote, requiring the ability to submit a token to the relying party; no special privileges or local access are necessary. Because the flaw centers on token validation, it represents a significant threat to confidentiality and integrity of authenticated sessions. The CVSS score of 9.1 indicates this flaw is rated as critical severity.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache CXF to at least version 4.2.3, 4.1.8, or 3.6.12 to apply the vendor fix.
  • Configure the OIDC token validator to reject self‑issued ID tokens unless explicitly enabled.
  • If self‑issued tokens are not required, disable their acceptance or enforce strict claim validation to eliminate the attack surface.

Generated by OpenCVE AI on August 6, 2026 at 17:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Apache
Apache cxf
Vendors & Products Apache
Apache cxf
Type Values Removed Values Added
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.
Title Apache CXF: Self-issued ID token claims validation skipped
Weaknesses CWE-345
References
Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Aug 7, 2026, 12:01 AM
Reserved
Jul 22, 2026, 9:50 AM
Status
Modified
Published
Aug 6, 2026, 12:16 PM
Modified
Oct 24, 2026, 4:10 PM