CVE-2026-13218 json
Kubevirt: kubevirt: symlink following in writetocachedfile allows host file overwrite from virt-launcher
published 4mo ago modified 4d ago also GHSA-q3jc-42cq-33fj , GO-2026-6914 , EUVD-2026-39594
- cvss
- 4.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-13218 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-13218 updated cvss 4.2
kubevirt: kubevirt: symlink following in WriteToCachedFile allows host file overwrite from virt-launcher
-
Red Hat OpenShift Virtualization 4 container-native-virtualization/virt-handler, container-native-virtualization/virt-handler-rhel9affected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.2 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L |
| GitHub | 3.1 | 4.2 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | kubevirt.io/kubevirt | <=1.10.0-rc.0 all versions |
no fix listed |
Affected products
- Red Hat Red Hat OpenShift Virtualization 4
Classification
- Weakness
-
- CWE-61 UNIX Symbolic Link (Symlink) Following
References
-
access.redhat.com
/security/cve/CVE-2026-13218
vdb-entry, web, vendor-advisory, mitigation
-
bugzilla.redhat.com
/show_bug.cgi?id=2492654
issue-tracking, web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-13218
advisory
-
github.com
/kubevirt/kubevirt
package
-
github.com
/kubevirt/kubevirt/blob/e63503d2f3a166f79f0891f8e1c3450eb39f88ac/pkg/network/cache/cache.go#L90-L103
web
-
github.com
/advisories/GHSA-q3jc-42cq-33fj
advisory
Sources
- CVE List CVE-2026-13218
- GitHub Advisory GHSA-q3jc-42cq-33fj
- NVD CVE-2026-13218
- OSV GO-2026-6914
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.