Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

nvd логотип

CVE-2026-13208

Опубликовано: 24 июн. 2026
Источник: nvd
CVSS3: 6.5
EPSS Низкий

Описание

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.

Уязвимые конфигурации

Конфигурация 1

Одно из

cpe:2.3:a:kubevirt:kubevirt:-:*:*:*:*:kubernetes:*:*
cpe:2.3:a:redhat:openshift_virtualization:*:*:*:*:*:*:*:*
Версия от 4 (включая) до 4.22.0 (включая)

EPSS

Процентиль: 1%
0.0009
Низкий

6.5 Medium

CVSS3

Дефекты

CWE-287

Связанные уязвимости

CVSS3: 6.5
redhat
около 2 месяцев назад

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.

msrc
около 1 месяца назад

Kubevirt: virt-handler-rhel9: kubevirt: virt-handler notify server trusts vmi identity from unauthenticated grpc request body

CVSS3: 6.5
github
около 2 месяцев назад

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.

EPSS

Процентиль: 1%
0.0009
Низкий

6.5 Medium

CVSS3

Дефекты

CWE-287