Skip to content
Fencer Intel
medium 4.7

CVE-2025-64432 json

KubeVirt Affected by an Authentication Bypass in Kubernetes Aggregation Layer

published last yr. modified last mo. also EUVD-2025-38218 , GHSA-38jw-g2qx-4286 , GO-2025-4103

cvss
4.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 3%
public exploits
0
none known

Summary

KubeVirt is a virtual machine management add-on for Kubernetes. Versions 1.5.3 and below, and 1.6.0 contained a flawed implementation of the Kubernetes aggregation layer's authentication flow which could enable bypass of RBAC controls. It was discovered that the virt-api component fails to correctly authenticate the client when receiving API requests over mTLS. In particular, it fails to validate the CN (Common Name) field in the received client TLS certificates against the set of allowed values defined in the extension-apiserver-authentication configmap. Failre to validate certain fields in the client TLS certificate may allow an attacker to bypass existing RBAC controls by directly communicating with the aggregated API server, impersonating the Kubernetes API server and its aggregator component. This issue is fixed in versions 1.5.3 and 1.6.1.

Patch / fix

  • go kubevirt.io/kubevirt 1.5.3, 1.6.0-beta.0.0.20250730135146-231dc69723f3, 1.6.1, 1.7.0-rc.0
  • kubevirt kubevirt 1.5.3, 1.6.1
  • kubevirt SLE Module for Containers 15 SP7 1.6.3-150700.3.13.1

suse advisories SUSE-SU-2025:4330-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

  • kubevirt Azure Linux 3.0 1.5.3-2
  • kubevirt CBL-Mariner 2.0 0.59.0-33

azure linux advisories AZL-69793AZL-69890

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2025-64432 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-64432 updated cvss 6.5

kubevirt.io/kubevirt: KubeVirt Authentication Bypass in Kubernetes Aggregation Layer

  • Red Hat OpenShift Virtualization 4 kubevirt, container-native-virtualization/virt-api, container-native-virtualization/virt-handler, container-native-virtualization/virt-launcher, container-native-virtualization/virt-operator, container-native-virtualization/virt-api-rhel9, +22 more Red Hat Web Terminal web-terminal/web-terminal-tooling-rhel9
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.15% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/kubevirt/kubevirt/security/advisories/GHSA-38jw-g2qx-4286 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go kubevirt.io/kubevirt
<1.5.3
>=1.6.0-alpha.0, <1.6.1
>=1.7.0-alpha.0, <1.7.0-rc.0
>=1.6.0-alpha.0, <1.6.0-beta.0.0.20250730135146-231dc69723f3
>=1.6.0-rc.0, <1.6.1
>=1.6.2, <1.7.0-rc.0
1.5.3
1.6.1
1.7.0-rc.0
1.6.0-beta.0.0.20250730135146-231dc69723f3

Affected products

  • kubevirt kubevirt

Classification

Weakness
  • CWE-287 Improper Authentication
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.