Red Hat Container Native Virtualization 4.14: Authorization Bypass Through User-Controlled Key
CVE-2026-17527 is a high-severity authorization bypass through user-controlled key vulnerability in Red Hat Container Native Virtualization 4.14 from Red Hat, with a CVSS 3.1 base score of 7.7 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.58% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Red Hat Container Native Virtualization 4.14 you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Red Hat | Red Hat Container Native Virtualization 4.14 | Not specified in the record | Not stated |
| Red Hat | Red Hat Container Native Virtualization 4.16 | Not specified in the record | Not stated |
| Red Hat | Red Hat Container Native Virtualization 4.17 | Not specified in the record | Not stated |
| Red Hat | Red Hat Container Native Virtualization 4.18 | Not specified in the record | Not stated |
| Red Hat | Red Hat Container Native Virtualization 4.19 | Not specified in the record | Not stated |
| Red Hat | Red Hat Container Native Virtualization 4.20 | Not specified in the record | Not stated |
| Red Hat | Red Hat Container Native Virtualization 4.21 | Not specified in the record | Not stated |
| Red Hat | Red Hat Container Native Virtualization 4.22 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Virtualization 4 | Not specified in the record | Not stated |
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
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. Scored by CNA (redhat.com).
Official description
In containerized-data-importer (CDI), the aggregated cdi.kubevirt.io:view ClusterRole, intended to provide read-only access to CDI resources, includes a rule granting create on the datavolumes/source subresource. CDI's DataVolume clone authorization accepts this permission as sufficient to authorize cloning the contents of any PVC the caller can name, without requiring write access to the source namespace. A user or service account bound to the view role, commonly granted cluster-wide via ClusterRoleBinding, who also has ordinary write access (edit/admin) to any single namespace, can use this to exfiltrate the contents of any PVC in the cluster into a namespace they control, bypassing namespace isolation and the read-only guarantee of the view role.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Authorization Bypass Through User-Controlled Key
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
How developers prevent this class of flaw
- For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
- Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
- Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
More Authorization Bypass Through User-Controlled Key vulnerabilities (CWE-639)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
- access.redhat.com/errata/RHSA-2026:59062
- access.redhat.com/errata/RHSA-2026:59083
- access.redhat.com/errata/RHSA-2026:59109
- access.redhat.com/errata/RHSA-2026:60117
- access.redhat.com/errata/RHSA-2026:60301
- access.redhat.com/errata/RHSA-2026:61666
- access.redhat.com/errata/RHSA-2026:62599
- access.redhat.com/errata/RHSA-2026:93958
- access.redhat.com/security/cve/CVE-2026-17527
- bugzilla.redhat.com/show_bug.cgi?id=2507413
Other vulnerabilities in Red Hat Container Native Virtualization 4.14
- 8.8 High severity
- 7.3 High severity
- 7.7 High severity
- 8.7 High severity
- 8.6 High severity
- 9.9 Critical severity
Recent Authorization Bypass Through User-Controlled Key vulnerabilities
- 9.3 Critical severity
- 7.1 High severity
- 8.3 High severity
- 8.1 High severity
- 8.8 High severity
- 9.6 Critical severity
Spotted an error? Tell us.