CVE-2025-14459: 
CBL Mariner vulnerability analysis and mitigation

CVE-2025-14459 is an authorization bypass vulnerability in KubeVirt's Containerized Data Importer (CDI), specifically in the virt-cdi-controller component. It allows a low-privileged user to clone PersistentVolumeClaims (PVCs) from unauthorized namespaces by exploiting the DataImportCron PVC source mechanism, resulting in unauthorized cross-namespace data access. The vulnerability was reported on December 10, 2025, and publicly disclosed on January 8, 2026, with a patch released via Red Hat Security Advisory RHSA-2026:0950 on January 22, 2026. It carries a CVSS v3.1 base score of 8.5 (High) (Red Hat CVE, Red Hat Bugzilla).

The root cause is classified as CWE-639 (Authorization Bypass Through User-Controlled Key), where the CDI controller fails to properly validate namespace boundaries when a DataImportCron resource specifies a PVC as its source. An authenticated user with low privileges can craft a DataImportCron object in their own namespace that references a PVC from any other namespace, and the controller will clone it without enforcing proper authorization checks. The attack is network-accessible, requires no user interaction, and has a changed scope (S:C), meaning the impact extends beyond the attacker's own namespace to affect other tenants in the cluster (Red Hat CVE, Red Hat Bugzilla).

Successful exploitation allows a low-privileged tenant in a multi-tenant Kubernetes/OpenShift cluster to read data from PVCs belonging to other namespaces they are not authorized to access, resulting in a high confidentiality impact. There is also a low integrity impact, as the cloning operation may create unauthorized copies of sensitive volumes. Availability is not directly affected. In shared cluster environments, this could expose sensitive workload data, secrets stored in volumes, or proprietary application data across tenant boundaries (Red Hat CVE, Feedly).

1. Reconnaissance: Identify a target cluster running Red Hat OpenShift Virtualization (CNV) 4.19 with the Containerized Data Importer (CDI) component enabled. Confirm that DataImportCron resources with PVC sources are supported.
2. Obtain low-privileged access: Authenticate to the cluster with any valid user account that has permission to create DataImportCron resources in at least one namespace.
3. Identify target PVC: Enumerate PVCs in other namespaces (e.g., via API calls or cluster-level list permissions) to identify a target PVC containing sensitive data.
4. Craft malicious DataImportCron: Create a DataImportCron resource in the attacker-controlled namespace with the spec.source.pvc field referencing the target PVC in the unauthorized namespace (e.g., namespace: victim-namespace, name: sensitive-pvc).
5. Trigger unauthorized clone: Submit the DataImportCron to the API server. The CDI controller processes the request without enforcing cross-namespace authorization, cloning the target PVC into the attacker's namespace.
6. Access cloned data: Mount the newly cloned PVC in an attacker-controlled pod and read its contents to exfiltrate sensitive data (Red Hat Bugzilla, Red Hat CVE).

• Kubernetes API Audit Logs: Unexpected CREATE events for DataImportCron resources in user namespaces where the spec.source.pvc references a PVC from a different namespace; look for cross-namespace PVC references in audit logs.
• Kubernetes API Audit Logs: Unexpected CREATE events for DataVolume or PVC clone operations initiated by the CDI controller (virt-cdi-controller) on behalf of a user-created DataImportCron targeting foreign namespaces.
• Resource Inventory: Presence of unexpected PVCs or DataVolume objects in a namespace that mirror PVCs from other namespaces, particularly if the owning user has no legitimate access to the source namespace.
• CDI Controller Logs: Log entries in the virt-cdi-controller pod showing clone operations initiated from a DataImportCron where the source PVC namespace differs from the DataImportCron namespace.

Red Hat has addressed this vulnerability in OpenShift Virtualization 4.19.17, released via security advisory RHSA-2026:0950 on January 22, 2026. Administrators should update to the patched container images provided in RHSA-2026:0950 for Red Hat Container Native Virtualization 4.19 on RHEL 9. As a workaround prior to patching, restrict RBAC permissions to prevent untrusted users from creating DataImportCron resources, and audit existing DataImportCron objects for cross-namespace PVC source references (Red Hat Advisory, Red Hat Bugzilla).

The vulnerability received coverage from The Hacker Wire, which published an article specifically on the unauthorized PVC cloning issue in KubeVirt CDI. Social media mentions appeared on Mastodon and Bluesky shortly after public disclosure. Overall community reaction has been measured, consistent with the lack of public exploit code and the relatively narrow affected audience (OpenShift Virtualization users) (The Hacker Wire).