No advisories yet.
Solution
No solution given by the vendor.
Workaround
Ensure virtual machines use the default masquerade network binding mode where possible. Restrict pods/exec access on virt-launcher pods to only trusted administrators. Review and restrict NetworkAttachmentDefinition resources to limit which namespaces can configure bridge-type network interfaces.
Fri, 26 Jun 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Thu, 25 Jun 2026 23:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in KubeVirt's virt-handler network cache handling. The WriteToCachedFile function writes data to a launcher-rooted path using os.WriteFile and os.Chown without symlink protection. A user with access to the virt-launcher container can plant a symlink at the cache file path, causing virt-handler to follow it and overwrite an arbitrary host file with JSON content and change its ownership. | |
| Title | Kubevirt: kubevirt: symlink following in writetocachedfile allows host file overwrite from virt-launcher | |
| 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-25T23:23:23.228Z
Reserved: 2026-06-24T15:29:58.096Z
Link: CVE-2026-13218
No data.
No data.
OpenCVE Enrichment
Updated: 2026-06-26T00:30:17Z