Answer in brief
CVE-2026-7374 records a Critical severity (CVSS 9.9) vulnerability in Kubevirt: kubevirt virt-handler: privilege escalation and node compromise via symlink following vulnerability. The current sources do not mark it as known exploited. The current feed maps kubevirt.io/kubevirt (go), kubevirt.io/kubevirt (go), kubevirt.io/kubevirt (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-7374 records a Critical severity (CVSS 9.9) vulnerability in Kubevirt: kubevirt virt-handler: privilege escalation and node compromise via symlink following vulnerability. The current sources do not mark it as known exploited. The current feed maps kubevirt.io/kubevirt (go), kubevirt.io/kubevirt (go), kubevirt.io/kubevirt (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps kubevirt.io/kubevirt (go), kubevirt.io/kubevirt (go), kubevirt.io/kubevirt (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| kubevirt.io/kubevirtgo | >=1.8.0-alpha.0,<1.8.3 | 1.8.3 |
| kubevirt.io/kubevirtgo | >=1.7.0-alpha.0,<1.7.4 | 1.7.4 |
| kubevirt.io/kubevirtgo | <1.6.6 | 1.6.6 |
Published upstream
May 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 30, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 9.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps kubevirt.io/kubevirt (go), kubevirt.io/kubevirt (go), kubevirt.io/kubevirt (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| kubevirt.io/kubevirtgo | >=1.8.0-alpha.0,<1.8.3 | 1.8.3 |
| kubevirt.io/kubevirtgo | >=1.7.0-alpha.0,<1.7.4 | 1.7.4 |
| kubevirt.io/kubevirtgo | <1.6.6 | 1.6.6 |
Published upstream
May 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 30, 2026
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.
Quoted source text, attributed separately from HOL analysis.