OpenShift Virtualization EUVD-2026-39599

Exploitation requires two specific conditions to be simultaneously true: the attacker must have shell or console access (PR:L) inside a running guest VM, and that VM must have the KubeVirt downward metrics feature enabled with its virtio-serial device exposed to the guest. The downward metrics device is not enabled by default on all VMs - it must be explicitly configured in the VirtualMachine spec. Exploitation is not possible from outside the guest (AV:L); unauthenticated network attackers cannot reach the virtio-serial endpoint. The feature must be present and the specific device node must be accessible from within the guest's OS user context. Limiting factors include: access is constrained to users with VM guest OS credentials, the downward metrics virtio-serial device must be explicitly provisioned, and exploitation rate is limited by host memory and cgroup constraints on virt-handler, which determine how quickly the OOM condition manifests.

The CVSS 3.1 score of 3.8 (Low) is consistent with the vector AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L. The local attack vector correctly captures that exploitation requires presence inside a guest VM - not a direct network path to the host. The scope-change flag (S:C) is the most operationally significant signal: virt-handler is a shared host-level process, so its OOM termination disrupts management of every VM on that Kubernetes node, not just the attacker's. EPSS data is not provided in the source intelligence, and the vulnerability is not listed in CISA KEV, indicating no confirmed mass exploitation or threat-actor use. No public proof-of-concept code has been identified. The primary real-world risk is an insider threat or a compromised guest workload in a multi-tenant OpenShift Virtualization cluster - a plausible but not imminent threat. The low CVSS score is accurate for isolated single-tenant deployments but understates risk in multi-tenant clusters where virt-handler serves many VMs and its OOM kill constitutes a broader denial-of-service event. There is no confidentiality or integrity impact confirmed.

A user with shell access to a VM guest that has the downward metrics virtio-serial device configured executes a simple command such as 'cat /dev/zero > /dev/virtio-ports/org.qemu.guest_agent.0' or writes a continuous stream to the appropriate virtio-serial device node. The virt-handler process on the Kubernetes node incrementally allocates heap memory for each byte received, and because no size limit or timeout is enforced, the process grows until the Linux OOM killer terminates it. No exploit code or proof-of-concept has been publicly identified, but the technique requires only standard guest OS write capabilities and no special tooling.