Microsoft security update for CVE-2026-13208 — azl3 kubevirt
🔗 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-13208. This page also shows what EchelonGraph holds for CVE-2026-13208, 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 products5
- 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
✅ 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 article | Update | Fixed build |
|---|---|---|
| — | Security Update | 1.8.4-1 |
| — | Security Update | 1.8.4-1 |
🧭 EchelonGraph on CVE-2026-13208
- EchelonGraph score
- 6.5 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 domain notify server. The gRPC handlers for HandleDomainEvent and HandleK8SEvent derive the VMI identity (namespace/name) solely from the request body without validating it against the connection's origin. Each virt-launcher pod connects through a per-VMI pipe socket, but no identity tag is propagated from the pipe path to the server handlers. This allows a compromised virt-launcher process to send forged domain lifecycle events for any other VMI scheduled on the same node, causing virt-handler to erroneously update that VMI's state and disrupt its lifecycle management.
Published by Red Hat, Inc., the CVE Numbering Authority that assigned CVE-2026-13208, 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).