CVE-2026-17527: Red Hat Container Native Virtualization 4.14 · Insecure Direct Object Reference
Affects Red Hat Container Native Virtualization 4.14Source CVE Database V5
Not known to be exploited · CVSS 7.7 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatRed Hat Container Native Virtualization 4.14 | Affected– | Fixed in– |
| Red HatRed Hat Container Native Virtualization 4.16 | Affected– | Fixed in– |
| Red HatRed Hat Container Native Virtualization 4.18 | Affected– | Fixed in– |
| Red HatRed Hat Container Native Virtualization 4.19 | Affected– | Fixed in– |
| Red HatRed Hat Container Native Virtualization 4.20 | Affected– | Fixed in– |
| Red HatRed Hat Container Native Virtualization 4.21 | Affected– | Fixed in– |
| Red HatRed Hat Container Native Virtualization 4.22 | Affected– | Fixed in– |
| Red HatRed Hat OpenShift Virtualization 4 | Affected– | Fixed in– |
AI-suggested
Until a fix is available, restrict granting the cdi.kubevirt.io:view ClusterRole cluster-wide and limit write access to namespaces to trusted users only to reduce risk.
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.
References
- access.redhat.com/security/cve/CVE-2026-17527 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2507413 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:59062 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:59083 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:59109 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60301 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60117 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:61666 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:62599 (opens in a new tab)