cve.bz

CVE-2026-13218 UNIX Symbolic Link (Symlink) Following

4.2 mediumEPSS 0.1%

Medium (4.2). EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

4.2 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-06-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-61 UNIX Symbolic Link (Symlink) Following
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-13218 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-13218?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-13218?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-13218 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-13218

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-13218](https://cve.bz/cve/badge/CVE-2026-13218.svg)](https://cve.bz/cve/CVE-2026-13218)

HTML:

<a href="https://cve.bz/cve/CVE-2026-13218"><img src="https://cve.bz/cve/badge/CVE-2026-13218.svg" alt="CVE-2026-13218"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
redhat:openshift_virtualizationfrom 4 through 4.22.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-q3jc-42cq-33fjGokubevirt.io/kubevirt<=1.10.0-rc.0no fix published
GO-2026-6914Gokubevirt.io/kubevirtall versionsno fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Azure Linux3kubevirtno fix listedAZL-91463
Azure Linux3kubevirt-openvmmno fix listedAZL-111647

From the distributions' data via OSV.dev: Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This flaw affects OpenShift Virtualization deployments where virtual machines are configured with bridge or other non-masquerade network interfaces. The default network binding mode in OpenShift Virtualization is masquerade, which does not trigger the vulnerable code path — exploitation requires a cluster administrator to have pre-configured a NetworkAttachmentDefinition with bridge-type binding, a condition beyond the attacker's control. Additionally, the attacker must have exec access to the virt-launcher container (not merely VM guest console access). The file content written by the exploit is constrained to valid JSON following the network cache schema — arbitrary byte injection is not possible. On OpenShift Container Platform, SELinux mandatory access controls in enforcing mode restrict the set of host files writable by the virt-handler process, and base OS binaries under /usr/ are protected by RHCOS read-only ostree layers. However, host configuration files under /etc/ and data under /var/ are potentially reachable depending on virt-handler's SELinux context. Red Hat rates this as Moderate impact because exploitation requires non-default network configuration, container-level access beyond standard VM user privileges, and the content constraint significantly limits the attacker's ability to achieve meaningful host compromise.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat OpenShift Virtualization 4container-native-virtualization/virt-handlerFix deferred
Red Hat OpenShift Virtualization 4container-native-virtualization/virt-handler-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-13218.

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON