CVSS 3.1
6.3 mediumCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:HMedium (6.3) in kubevirt kubevirt. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in kubevirt.io/kubevirt 1.5.3, 1.6.0-beta.0.0.20250730135146-231dc69723f3, 1.6.1.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:Hkubevirt.io/kubevirt (Go): fixed in 1.5.3, 1.6.1, 1.6.0-beta.0.0.20250730135146-231dc69723f3Explain CVE-2025-64434 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-64434?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-64434?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-64434 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| kubevirt:kubevirt | before 1.5.3 |
| kubevirt:kubevirt | 1.6.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-ggp9-c99x-54gp | Go | kubevirt.io/kubevirt | <1.5.3 | 1.5.3 |
| GHSA-ggp9-c99x-54gp | Go | kubevirt.io/kubevirt | >=1.6.0-alpha.0 <1.6.1 | 1.6.1 |
| GO-2025-4107 | Go | kubevirt.io/kubevirt | <1.5.3 >=1.6.0-alpha.0 <1.6.0-beta.0.0.20250730135146-231dc69723f3 >=1.6.0-rc.0 <1.6.1 | 1.5.3, 1.6.0-beta.0.0.20250730135146-231dc69723f3, 1.6.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| SUSE | Linux Enterprise Module for Containers 15 SP7 | kubevirt | 1.6.3-150700.3.13.1 | SUSE-SU-2025:4330-1 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-SU-2026:21483-1 |
| Azure Linux | 2 | kubevirt | 0.59.0-33 | AZL-69961 |
| Azure Linux | 3 | kubevirt | 1.5.3-2 | AZL-69796 |
From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.
Red Hat rates this Moderate.
The impact oF this vulnerability is rated MODERATE because successful exploitation requires first compromising a privileged virt-handler component, which is not directly accessible to untrusted users and requires prior breach of Kubernetes node or container security boundaries.
he vulnerability stems from shared credentials and inadequate validation that allows a compromised virt-handler to present itself as the legitimate virt-api service when communicating with other virt-handler instances. An attacker who successfully compromises a single virt-handler - a privileged Kubernetes DaemonSet component running on each node, can exploit this authentication weakness to perform lateral movement within the cluster, executing privileged operations on VMs managed by other virt-handler instances on different nodes.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift Virtualization 4 | kubevirt | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-64434.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.