CVE-2026-13201Kubevirt: virt-handler-rhel9: kubevirt: safepath symlink following in virt-handler enables notify socket hijacking and node-level vm disruption
Updated under an hour ago ()
Does this affect you?
It affects Red Hat Container Native Virtualization 4.12 and 2 other products. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
A flaw was found in KubeVirt's safepath package used by virt-handler. The OpenAtNoFollow function uses O_PATH|O_NOFOLLOW to obtain a file descriptor to a path leaf, but downstream operations resolve the path via /proc/self/fd/N using link-following syscalls. When the leaf is a symlink, the kernel dereferences it, defeating the intended no-follow protection. An attacker with access to a virt-launcher pod can exploit this to redirect virt-handler's IPC socket connections, including the notify socket used for VM domain lifecycle events. By hijacking this socket, the attacker can inject arbitrary domain events into virt-handler, causing it to take incorrect lifecycle actions, corrupt VM state in the Kubernetes API, or crash — resulting in sustained denial of VM management services for all virtual machines on the affected node. Additionally, the same symlink following flaw allows virt-handler to apply file ownership or permission changes to unintended host paths.
- CVSS
- 7.3 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H
- Weakness (CWE)
- CWE-61
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- redhat
- NVD analysis
- Modified
- Record last updated
- Oct 12, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Red Hat Red Hat Container Native Virtualization 4.12 redhat:container_native_virtualization | from 1791522624 not affected | CNA record |
kubevirt kubevirt kubevirt:kubevirt | all versions | NVD |
redhat openshift_virtualization redhat:openshift_virtualization | from 4 through 4.22.0 | NVD |
References
- https://access.redhat.com/errata/RHSA-2026:51031vendor-advisory, x-refsource-redhat
- https://access.redhat.com/errata/RHSA-2026:53655vendor-advisory, x-refsource-redhat
- https://access.redhat.com/errata/RHSA-2026:53671vendor-advisory, x-refsource-redhat
- https://access.redhat.com/errata/RHSA-2026:53684vendor-advisory, x-refsource-redhat
- https://access.redhat.com/errata/RHSA-2026:53721vendor-advisory, x-refsource-redhat
- https://access.redhat.com/errata/RHSA-2026:53728vendor-advisory, x-refsource-redhat
- https://access.redhat.com/errata/RHSA-2026:53763vendor-advisory, x-refsource-redhat
- https://access.redhat.com/errata/RHSA-2026:53797vendor-advisory, x-refsource-redhat
- https://access.redhat.com/errata/RHSA-2026:53826vendor-advisory, x-refsource-redhat
- https://access.redhat.com/errata/RHSA-2026:53838vendor-advisory, x-refsource-redhat
- https://access.redhat.com/errata/RHSA-2026:80941vendor-advisory, x-refsource-redhat
- https://access.redhat.com/security/cve/CVE-2026-13201vdb-entry, x-refsource-redhat, mitigation, vendor-advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2492203issue-tracking, x-refsource-redhat, vendor-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.