---
id: CVE-2026-13208
title: A flaw was found in KubeVirt's virt-handler domain notify server
summary: >-
  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 connecti…
severity: medium
cvss: 6.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H'
cwe:
  - CWE-287
vendor: kubevirt
product: kubevirt
affected:
  - kubevirt
  - 'openshift_virtualization >= 4, <= 4.22.0'
published: '2026-06-24'
updated: '2026-07-06'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-13208'
references:
  - url: 'https://access.redhat.com/security/cve/CVE-2026-13208'
    label: secalert@redhat.com
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2492220'
    label: secalert@redhat.com
tags:
  - nvd
epss: 0.00126
epssPercentile: 0.01921
ingestedAt: '2026-07-06T18:45:21.295Z'
---

## Overview

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

- `kubevirt`
- `openshift_virtualization >= 4, <= 4.22.0`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
