CVE-2026-13208
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.
Summary dbcve.org
In KubeVirt's virt-handler, the gRPC handlers HandleDomainEvent and HandleK8SEvent derive VMI identity (namespace/name) solely from the request body without validating it against the connection origin. Each virt-launcher pod connects via a per-VMI pipe socket, but no identity tag propagates from the pipe path to the server. A compromised virt-launcher can forge domain lifecycle events for any other VMI on the same node, causing virt-handler to erroneously update that VMI's state.
Mitigation
Implement origin validation in virt-handler gRPC handlers to verify that the claimed VMI identity matches the authenticated connection origin (e.g., validate against pipe socket path metadata or add mutual TLS authentication between virt-launcher and virt-handler).