CVE-2026-13622
A symlink following vulnerability was found in KubeVirt's …
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 now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- access.redhat.com/security/cve/CVE-2026-13622
- bugzilla.redhat.com/show_bug.cgi?id=2494142
- access.redhat.com/errata/RHSA-2026:51031
- access.redhat.com/errata/RHSA-2026:53655
- access.redhat.com/errata/RHSA-2026:53671
- access.redhat.com/errata/RHSA-2026:53684
- access.redhat.com/errata/RHSA-2026:53763
- access.redhat.com/errata/RHSA-2026:53838
- nvd.nist.gov/vuln/detail/CVE-2026-13622
- cve.org/CVERecord?id=CVE-2026-13622
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.