KUBEVIRT.IO/KUBEVIRT · CVE-2026-13218 · Infrastructure
NO FIX YET
KubeVirt's virt-handler writes network cache files without checking for symlinks, so a user in the virt-launcher container can plant a symlink and make virt-handler overwrite an arbitrary host file. The attacker also controls the file's ownership change, which can be used to break host integrity.
first public Jun 26, 2026 · 2 sources
Running Kubevirt.io/kubevirt? Find out in 2 minutes.
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Clusters running KubeVirt at or below 1.10.0-rc.0, where virt-handler runs on nodes alongside virt-launcher pods that tenants can access. Exposure needs a user with access to the virt-launcher container; clusters without untrusted workloads on KubeVirt are lower risk. The sources do not state a fixed version.
Not affected if no-untrusted-vm-users, version-above-affected-range
Who cares cwe-61, kubernetes, kubevirt, virtualization
kubectl get kubevirt -n kubevirt -o jsonpath='{.items[0].status.observedKubeVirtVersion}'go:kubevirt.io/kubevirt up to and including 1.10.0-rc.0No fix yet, per the sources.
A flaw was found in KubeVirt's virt-handler network cache handling. The writeToCachedFile function writes data to a launcher-rooted path using os.WriteFile and os.Chown without symlink protection. A user with access to the virt-launcher container can plant a symlink at the cache file path, causing virt-handler to follow it and overwrite an arbitrary host file with JSON content and change its ownership.
This page as .md · .json · in your agent: get_signal("CVE-2026-13218") · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.