Symlink Attack Affecting github.com/kubevirt/kubevirt/pkg/virt-handler/isolation package, versions <1.5.3>=1.6.0-alpha.0 <1.6.1
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-GOLANG-GITHUBCOMKUBEVIRTKUBEVIRTPKGVIRTHANDLERISOLATION-13863413
- published9 Nov 2025
- disclosed7 Nov 2025
- creditSébastien Rolland, Mihail Kirov
Introduced: 7 Nov 2025
NewCVE-2025-64437 Â (opens in a new tab)How to fix?
Upgrade github.com/kubevirt/kubevirt/pkg/virt-handler/isolation to version 1.5.3, 1.6.1 or higher.
Overview
Affected versions of this package are vulnerable to Symlink Attack due to failing to verify whether launcher-sock is a symlink or a regular file. An attacker that can access a virt-launcher pod's file system and has access to the host file system with the privileges of the qemu user and can create unprivileged user namespaces, can change the ownership of arbitrary files on the host node to an unprivileged user.