Apache CXF: Insufficient Verification of Data Authenticity
CVE-2026-65583 is a critical-severity insufficient verification of data authenticity vulnerability in Apache CXF from Apache, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 4.2.3, 4.1.8, 3.6.12 as the first without the flaw, so updating Apache CXF to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.28% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Apache CXF to 4.2.3 or 4.1.8 or 3.6.12, whichever matches your release line, or a later version.
- Update Cxf to 3.6.12 or 4.1.8 or 4.2.3, whichever matches your release line, or a later version.
- Read the advisory on lists.apache.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | Apache CXF | 4.2.0 up to, but not including, 4.2.3; 4.0.0 up to, but not including, 4.1.8; before 3.6.12 | 4.2.3, 4.1.8, 3.6.12 |
| Apache | Cxf | before 3.6.12; 4.0.0 up to, but not including, 4.1.8; 4.2.0 up to, but not including, 4.2.3 | 3.6.12, 4.1.8, 4.2.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by CISA (ADP).
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insufficient Verification of Data Authenticity
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
More Insufficient Verification of Data Authenticity vulnerabilities (CWE-345)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
Other vulnerabilities in Apache CXF
- 7.5 High severity
- 9.1 Critical severity
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
- 9.1 Critical severity
Recent Insufficient Verification of Data Authenticity vulnerabilities
- 7.5 High severity
- 9.1 Critical severity
- 9.1 Critical severity
- 7.7 High severity
- 8.5 High severity
- 7.6 High severity
Spotted an error? Tell us.