Incorrect Authorization Affecting kubevirt package, versions *


Severity

Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.61% (47th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-KUBEVIRT-9889891
  • published28 Apr 2025
  • disclosed15 Mar 2023

Introduced: 15 Mar 2023

CVE-2023-26484  (opens in a new tab)
CWE-863  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:10 kubevirt.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kubevirt package and not the kubevirt package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

KubeVirt is a virtual machine management add-on for Kubernetes. In versions 0.59.0 and prior, if a malicious user has taken over a Kubernetes node where virt-handler (the KubeVirt node-daemon) is running, the virt-handler service account can be used to modify all node specs. This can be misused to lure-in system-level-privileged components which can, for instance, read all secrets on the cluster, or can exec into pods on other nodes. This way, a compromised node can be used to elevate privileges beyond the node until potentially having full privileged access to the whole cluster. The simplest way to exploit this, once a user could compromise a specific node, is to set with the virt-handler service account all other nodes to unschedulable and simply wait until system-critical components with high privileges appear on its node. No patches are available as of time of publication. As a workaround, gatekeeper users can add a webhook which will block the virt-handler service account to modify the spec of a node.

CVSS Base Scores

version 3.1