No advisories yet.
Solution
No solution given by the vendor.
Workaround
The following default configurations in OpenShift Virtualization significantly reduce exploitability and impact: 1. Ensure SELinux is in enforcing mode (default in OpenShift). This restricts the set of host files that virt-handler can modify through this path, blocking operations on files with protected security labels. 2. RHCOS immutable filesystem layers prevent modification of core OS files. 3. Review RBAC policies to limit unnecessary pods/exec permissions on virt-launcher pods to reduce the attacker pool.
Wed, 24 Jun 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in KubeVirt's safepath package. The OpenAtNoFollow function uses O_PATH|O_NOFOLLOW to obtain a file descriptor to a path leaf, but downstream helpers operate 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 cause virt-handler to apply file ownership or permission changes to an unintended host path. | |
| Title | Kubevirt: virt-handler-rhel9: kubevirt: safepath openatnofollow symlink following via /proc/self/fd allows host file metadata modification | |
| First Time appeared |
Redhat
Redhat container Native Virtualization |
|
| Weaknesses | CWE-61 | |
| CPEs | cpe:/a:redhat:container_native_virtualization:4 | |
| Vendors & Products |
Redhat
Redhat container Native Virtualization |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-06-24T20:39:00.173Z
Reserved: 2026-06-24T13:58:29.925Z
Link: CVE-2026-13201
No data.
No data.
No data.
OpenCVE Enrichment
No data.