CVE-2026-65583
Apache Cxf authentication bypass
- Published6 Aug 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-65583 being actively exploited?
CVE-2026-65583 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.28%.
How severe is CVE-2026-65583?
CVE-2026-65583 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.28% probability of exploitation.
Which products are affected by CVE-2026-65583?
Affected products include Apache Cxf.
How do I fix CVE-2026-65583?
Upgrade affected software to a fixed version, for example Apache Cxf 4.1.8 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-65583 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.