Description
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.
Affected products
kubevirt: kubevirt; redhat: openshift virtualization
References2
- access.redhat.com/security/cve/CVE-2026-13208 MitigationVendor Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2492220 Issue TrackingVendor Advisory
Metrics
- CVSS 3.1
-
6.5
MEDIUM
Score source: CNA
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H - EPSS — exploit probability
- 0% percentile: 2 · as of 16 November 2026
- CWE
- CWE-287
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.