Critical privilege escalation in OpenShift/KubeVirt virtualization that can take control of a node and cluster.
CVE-2026-7374
Auth OpenShift user can hijack virt-handler via symlink to host CRI-O socket, gaining node access.
Is CVE-2026-7374 being exploited?
Not confirmed. CVE-2026-7374 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.74% probability of exploitation in the next 30 days.
How severe is CVE-2026-7374?
CVE-2026-7374 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-7374?
Yes. A fix has been recorded for CVE-2026-7374. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-7374 affect?
CVE-2026-7374 affects KubeVirt virt-handler, OpenShift Virtualization, Kubernetes with KubeVirt. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-7374?
Patch when available; restrict edit perms and namespace access; monitor socket activity
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Access to any host Unix socket; potential full node and cluster compromise via privileged virt-handler.
Immediate action required