CVE-2026-13218MediumMicrosoft CVSS 4.2CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L

Microsoft security update for CVE-2026-13218 — azl3

Published
July 1, 2026
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-13218. This page also shows what EchelonGraph holds for CVE-2026-13218, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products7

  • azl3 kubevirt 1.7.1-7 on Azure Linux 3.0
  • azl3 kubevirt 1.7.1-8 on Azure Linux 3.0
  • azl3 kubevirt 1.8.4-1 on Azure Linux 3.0
  • azl3 kubevirt 1.8.4-2 on Azure Linux 3.0
  • azl3 kubevirt 1.8.4-4 on Azure Linux 3.0
  • azl3 kubevirt 1.8.4-5 on Azure Linux 3.0
  • azl3 kubevirt-openvmm 1.9.0-1 on Azure Linux 3.0

✅ Updates Microsoft lists: 2 updates

2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update—
—Security Update—

🧭 EchelonGraph on CVE-2026-13218

EchelonGraph score
4.2 MEDIUM
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

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 by Red Hat, Inc., the CVE Numbering Authority that assigned CVE-2026-13218, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)