Back to CVE records
Medium 6.5Published Jun 24, 2026

CVE-2026-13208A flaw was found in KubeVirt's virt-handler domain notify server.

Updated under an hour ago ()

Does this affect you?

It affects kubevirt and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
6.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
Weakness (CWE)
CWE-287
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Not given
NVD analysis
Analyzed
Record last updated
Jul 6, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
kubevirt kubevirt
kubevirt:kubevirt
all versions
NVD
redhat openshift_virtualization
redhat:openshift_virtualization
from 4 through 4.22.0
NVD

References

  • mitigation, vendor-advisory
  • issue-tracking, vendor-advisory

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.