CVE-2026-13218: Kubevirt: kubevirt: symlink following in writetocachedfile allows host file overwrite from virt-launcher
A flaw was found in KubeVirt's network cache handling in virt-handler. The WriteToCachedFile function in pkg/network/cache/cache.go writes network cache data to a path under /proc/<launcherPid>/root/var/run/kubevirt-private/ using os.WriteFile and then changes ownership using os.Chown. Neither operation uses ONOFOLLOW or the safepath package to prevent symlink traversal. Since virt-handler operates in the host mount namespace (only the network namespace is entered via setns), a symlink planted by a compromised virt-launcher process at the cache file path causes virt-handler to follow the symlink and write to an arbitrary host file, overwriting its content with JSON data and changing its ownership to uid 107. This constitutes a container-to-host file write primitive, though with constrained content (serialized JSON network cache data). The vulnerable code path is triggered only for bridge/non-masquerade interfaces (via the discoverbridge path in vm.go -> netconf.go -> cache.go). The default masquerade binding does not exercise this path.
Other 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.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-13218?
The severity of CVE-2026-13218 is classified as medium with a score of 4.2.
What does CVE-2026-13218 impact?
CVE-2026-13218 impacts KubeVirt's virt-handler network cache handling.
How can I mitigate CVE-2026-13218?
To mitigate CVE-2026-13218, avoid granting unnecessary access to the virt-launcher container.
What is the main issue described in CVE-2026-13218?
The main issue in CVE-2026-13218 is a flaw in the WriteToCachedFile function that allows symlink following, leading to potential host file overwriting.
Who is affected by CVE-2026-13218?
Users with access to the virt-launcher container are affected by CVE-2026-13218.