KubeVirt CVE-2026-13218

Exploitation requires that the attacker hold active access to the virt-launcher container (e.g., shell access via kubectl exec or a guest escape), sufficient to create a symlink at the specific filesystem path used by virt-handler's WriteToCachedFile for network cache storage. The symlink must be planted before virt-handler performs its next cache write operation, introducing a timing dependency that contributes to AC:H. The vulnerability is limited to environments where KubeVirt is deployed and virt-handler and virt-launcher are co-resident on the same node. Exploitation is constrained to overwriting files with valid JSON content and changing file ownership - arbitrary binary writes are not possible. Host files that are not accessible from the path virt-handler uses cannot be targeted. No network-facing or unauthenticated exploitation path exists; the CVSS vector (AV:L/PR:L) confirms a local, low-privilege prerequisite.

The official CVSS 3.1 score of 4.2 (Medium) reflects the realistic exploitation difficulty. AV:L confirms local access is required - specifically, access to the virt-launcher container - and AC:H acknowledges the race-condition or timing window inherent in planting the symlink before virt-handler performs the write. PR:L indicates that low-privilege container access is sufficient. The scope change (S:C) is the most significant risk signal: successful exploitation allows a container workload to influence the host filesystem, which in hardened Kubernetes environments represents a meaningful boundary violation. The impact is constrained: content written is JSON-formatted (attacker-influenced but not arbitrary binary), and only integrity (I:L) and availability (A:L via ownership corruption) are affected - confidentiality is not impacted. No EPSS score, KEV status, or POC was present in the input data, so exploitation probability cannot be quantified beyond the CVSS signals. The combination of high complexity and local-only access substantially limits opportunistic exploitation, but in multi-tenant Kubernetes environments where untrusted workloads run alongside KubeVirt, the container-to-host write primitive warrants patching as part of normal vulnerability management. No conflicting signals were detected between the CVSS vector and the description.

An attacker who has gained shell access inside a virt-launcher VM pod - for example, through a guest escape or a compromised containerized workload - identifies the filesystem path where virt-handler writes its network cache file. The attacker replaces or pre-creates that path as a symlink pointing to a sensitive host file such as /etc/cron.d/kubevirt or a kubeconfig. When virt-handler next invokes WriteToCachedFile, it follows the symlink and overwrites the host target with JSON content, potentially corrupting the file and transferring ownership to a container-controlled UID, degrading host-level services or enabling further privilege escalation.