CVE-2026-7374: Kubevirt: kubevirt virt-handler: privilege escalation and node compromise via symlink following vulnerability
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-7374 is a critical KubeVirt virt-handler flaw in Red Hat Container Native Virtualization. A user with edit rights in one OpenShift namespace could potentially turn limited access into host node and cluster control by abusing symlink handling around VM console sockets.
Executive priority
Treat as urgent for OpenShift virtualization environments. The vulnerability can convert ordinary namespace edit access into potential node and cluster takeover. Patch planning should be immediate, with temporary RBAC tightening where updates cannot be applied quickly.
Technical view
The flaw is CWE-59 improper symlink following in virt-handler. An authenticated namespace editor can replace a VM console socket with a symlink to a host Unix socket such as CRI-O. virt-handler’s privileged connection may then be hijacked, enabling access to host sockets and potential node or cluster compromise.
Likely exposure
Exposure is most relevant to OpenShift clusters running Red Hat Container Native Virtualization 4.12 through 4.21 as listed, with KubeVirt virt-handler deployed and users granted namespace edit permissions. One affected entry appears inconsistent: product says 4.2 while CPE indicates 4.20.
Exploitation context
The attacker needs authenticated OpenShift access with edit permissions in a single namespace. The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. The impact is severe because compromise can cross from namespace-level access to the host and cluster.
Researcher notes
Sources provide mechanism, CVSS 9.9, affected CNV versions, and Red Hat advisories, but not detailed fixed package mapping in the bundle. Avoid assuming exploit availability. Validate directly against Red Hat CVE, CSAF/VEX, Bugzilla, and the relevant RHSA for each deployed version.
Mitigation direction
Apply the relevant Red Hat RHSA update for your CNV version.
Review Red Hat CVE guidance for fixed package versions and deployment instructions.
Restrict namespace edit permissions to trusted users only.
Audit VM console access and KubeVirt administrative permissions.
Prioritize clusters hosting sensitive workloads or shared tenant namespaces.
Validation and detection
Inventory Red Hat Container Native Virtualization versions across OpenShift clusters.
Confirm whether virt-handler packages match affected versions listed by Red Hat.
Check whether applicable RHSA advisories are installed.
Review RBAC for users with edit access in VM namespaces.
Monitor for suspicious VM console socket or host socket access activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-59: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
7Timeline events
2ADP providers
14Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-59 · source CWE mapping
Improper Link Resolution Before File Access ('Link Following')
Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.