# CVE-2025-14459: Virt-cdi-controller: unauthorized pvc cloning via dataimportcron

> Attackers can clone PersistentVolumeClaims from unauthorized namespaces via DataImportCron, leading to unauthorized data access in KubeVirt environments.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jan 2026
- **Updated:** 15 Jul 2026
- **Also known as:** AZL-75395, AZL-75404, AZL-75443, AZL-75446, AZL-75494, GHSA-727r-mf78-ghxp

## What is CVE-2025-14459?

CVE-2025-14459 is a high-severity missing authorization vulnerability in Red Hat RHEL-9-CNV-4.19, published on 26 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in KubeVirt Containerized Data Importer (CDI). This vulnerability allows a user to clone PersistentVolumeClaims (PVCs) from unauthorized namespaces, resulting in unauthorized access to data via the DataImportCron PVC source mechanism.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2025-14459?


## How do I fix CVE-2025-14459?

Apply the vendor's patch.

## Is CVE-2025-14459 being exploited?

There is no known exploitation of CVE-2025-14459 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14459 and fix it if it is affected.

What it is: CVE-2025-14459 is a high-severity missing authorization vulnerability in Red Hat RHEL-9-CNV-4.19, published on 26 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14459 in the wild and no public exploit code.

Affected product: Red Hat RHEL-9-CNV-4.19. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14459/ (Markdown: https://insights.sbomify.com/CVE-2025-14459/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14459
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14459
- OSV: https://osv.dev/vulnerability/CVE-2025-14459

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14459/
Summaries are generated and may contain mistakes; the official description above is the record.