A flaw was found in KubeVirt's virt-handler component. This vulnerability allows an authenticated OpenShift user with edit permissions in a single namespace to exploit improper symlink validation when connecting to virtual machine console sockets. By replacing the console socket with a symlink to the host's container runtime (CRI-O) socket, an attacker can hijack virt-handler's privileged connection. This enables the attacker to access any Unix socket on the host, potentially leading to full control of the node and the entire cluster.
A flaw was found in KubeVirt's virt-handler component. This vulnerability allows an authenticated OpenShift user with edit permissions in a single namespace to exploit improper symlink validation when connecting to virtual machine console sockets. By replacing the console socket with a symlink to the host's container runtime (CRI-O) socket, an attacker can hijack virt-handler's privileged connection. This enables the attacker to access any Unix socket on the host, potentially leading to full control of the node and the entire cluster.
A flaw was found in KubeVirt's virt-handler component. This vulnerability allows an authenticated OpenShift user with edit permissions in a single namespace to exploit improper symlink validation when connecting to virtual machine console sockets. By replacing the console socket with a symlink to the host's container runtime (CRI-O) socket, an attacker can hijack virt-handler's privileged connection. This enables the attacker to access any Unix socket on the host, potentially leading to full control of the node and the entire cluster.
A flaw was found in KubeVirt's virt-handler component. This vulnerability allows an authenticated OpenShift user with edit permissions in a single namespace to exploit improper symlink validation when connecting to virtual machine console sockets. By replacing the console socket with a symlink to the host's container runtime (CRI-O) socket, an attacker can hijack virt-handler's privileged connection. This enables the attacker to access any Unix socket on the host, potentially leading to full control of the node and the entire cluster.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: May 26, 2026, 1:14:53 PM
dateUpdated: Sep 10, 2026, 12:05:01 PM
13 related source bulletins · separate from aliases
RHSA-2026:20736: Red Hat Security Advisory: OpenShift Virtualization v4.18 Images
CVE-2026-7374
SUSE-SU-2026:2077-1: Security update for kubevirt
CVE-2026-7374
msrc_CVE-2026-7374: Kubevirt: kubevirt virt-handler: privilege escalation and node compromise via symlink following vulnerability
CVE-2026-7374
RHSA-2026:20763: Red Hat Security Advisory: OpenShift Virtualization v4.17 Images
CVE-2026-7374
RHSA-2026:20890: Red Hat Security Advisory: OpenShift Virtualization v4.14 Images
CVE-2026-7374
RHSA-2026:20782: Red Hat Security Advisory: OpenShift Virtualization v4.20 Images
CVE-2026-7374
RHSA-2026:20886: Red Hat Security Advisory: OpenShift Virtualization v4.13 Images
CVE-2026-7374
RHSA-2026:20975: Red Hat Security Advisory: OpenShift Virtualization v4.16 Images
CVE-2026-7374
RHSA-2026:20866: Red Hat Security Advisory: OpenShift Virtualization v4.15 Images
CVE-2026-7374
WID-SEC-W-2026-1680: Red Hat OpenShift Virtualization: Schwachstelle ermöglicht Privilegieneskalation
CVE-2026-7374
RHSA-2026:20720: Red Hat Security Advisory: OpenShift Virtualization v4.21 Images
CVE-2026-7374
RHSA-2026:20767: Red Hat Security Advisory: OpenShift Virtualization v4.19 Images
CVE-2026-7374
RHSA-2026:20825: Red Hat Security Advisory: OpenShift Virtualization v4.12 Images
CVE-2026-7374
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Awaiting Analysis
Weakness classifications: CWE-59
Original publisher date fields
published: 2026-05-26T14:16:40.717
lastModified: 2026-09-10T13:20:31.720
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.