CVE-2026-13218: Kubevirt: kubevirt: symlink following in writetocachedfile allows host file overwrite from virt-launcher
Noroxi assessment
Priority: Monitor (action score 16/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: azl3 kubevirt 1.8.4-2 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to azl3 kubevirt 1.8.4-2 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 26, 2026
- Updated
- Oct 25, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-61
Report tools
Action score
16
Low priority for now.
- CVSS
- 16 / 40 · 4.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · redhat
- 4.2
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| kubevirt | kubevirt | cpe:2.3:a:kubevirt:kubevirt |
| redhat | openshift virtualization | cpe:2.3:a:redhat:openshift_virtualization |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Red Hat Red Hat OpenShift Virtualization 4
- all versionsaffected
- all versionsaffected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- kubevirt kubevirtall versions
- redhat openshift virtualization4 and later · up to 4.22.0 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | kubevirt.io/kubevirt | from 0 | — |
| Go | kubevirt.io/kubevirt | up to and including 1.10.0-rc.0 | — |
Same product
kubevirt: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-14316A flaw was found in kubevirt 0.29 and earlier.39Monitor
- CVE-2025-64324KubeVirt Vulnerable to Arbitrary Host File Read and Write34Monitor
- CVE-2023-26484On a compromised KubeVirt node, the virt-handler service account can be used to modify all node specs32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-13201Jun 24, 2026 · Kubevirt: virt-handler-rhel9: kubevirt: safepath symlink following in virt-handler enables notify socket hijacking and node-level vm disruption29Monitor
- ← EarlierCVE-2026-13208Jun 24, 2026 · Kubevirt: virt-handler-rhel9: kubevirt: virt-handler notify server trusts vmi identity from unauthenticated grpc request body26Monitor
- Later →CVE-2026-13318Jun 26, 2026 · Virt-api-rhel9: kubevirt: kubevirt: ssrf in virt-api port-forward via unvalidated guest-agent-reported ip25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 kubevirt 1.8.4-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kubevirt 1.8.4-2 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-132012 days apartKubevirt: virt-handler-rhel9: kubevirt: safepath symlink following in virt-handler enables notify socket hijacking and node-level vm disruption29Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-61 · UNIX Symbolic Link (Symlink) FollowingCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.