CVE-2025-64433· NVD / CVE Program· CNA GitHub_M

KubeVirt Arbitrary Container File Read

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.52% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: kubevirt kubevirt 1.5.3; azl3 kubevirt 1.5.0-5 on Azure Linux 3.0 1.5.3-2; cbl2 kubevirt 0.59.0-31 on CBL Mariner 2.0 0.59.0-33.

Low priority for now. Upgrade to kubevirt kubevirt 1.5.3; azl3 kubevirt 1.5.0-5 on Azure Linux 3.0 1.5.3-2; cbl2 kubevirt 0.59.0-31 on CBL Mariner 2.0 0.59.0-33 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

KubeVirt is a virtual machine management add-on for Kubernetes. Prior to 1.5.3 and 1.6.1, a vulnerability was discovered that allows a VM to read arbitrary files from the virt-launcher pod's file system. This issue stems from improper symlink handling when mounting PVC disks into a VM. Specifically, if a malicious user has full or partial control over the contents of a PVC, they can create a symbolic link that points to a file within the virt-launcher pod's file system. Since libvirt can treat regular files as block devices, any file on the pod's file system that is symlinked in this way can be mounted into the VM and subsequently read. Although a security mechanism exists where VMs are executed as an unprivileged user with UID 107 inside the virt-launcher container, limiting the scope of accessible resources, this restriction is bypassed due to a second vulnerability. The latter causes the ownership of any file intended for mounting to be changed to the unprivileged user with UID 107 prior to mounting. As a result, an attacker can gain access to and read arbitrary files located within the virt-launcher pod's file system or on a mounted PVC from within the guest VM. This vulnerability is fixed in 1.5.3 and 1.6.1.

MediumCVSS 6.5 · v3.1—No exploit Fix available

Path traversal

Published: Nov 7, 2025
Updated: Jun 17, 2026
EPSS: 0.5% · 43th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 6.5; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
kubevirt	kubevirt	cpe:2.3:a:kubevirt:kubevirt

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

kubevirt kubevirtbefore 1.5.3
kubevirt kubevirt1.6.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

kubevirt kubevirt
- < 1.5.3, >= 1.6.0-alpha.0, < 1.6.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	kubevirt.io/kubevirt	from 1.6.0-alpha.0 · before 1.6.1	1.6.1
Go	kubevirt.io/kubevirt	from 1.6.0-alpha.0 · before 1.6.0-beta.0.0.20250801195231-a81b27d4600c	1.6.0-beta.0.0.20250801195231-a81b27d4600c
Go	kubevirt.io/kubevirt	from 1.6.0-rc.0 · before 1.6.1	1.6.1
Go	kubevirt.io/kubevirt	before 1.5.3	1.5.3
openSUSE:Leap 16.0	kubevirt	before 1.7.0-160000.1.1	1.7.0-160000.1.1
openSUSE:Tumbleweed	kubevirt	before 1.6.3-1.1	1.6.3-1.1
openSUSE:Tumbleweed	kubevirt-1.8	before 1.8.3-1.1	1.8.3-1.1
openSUSE:Tumbleweed	kubevirt1.8	before 1.8.3-1.1	1.8.3-1.1
SUSE:Linux Enterprise Module for Containers 15 SP7	kubevirt	before 1.6.3-150700.3.13.1	1.6.3-150700.3.13.1
SUSE:Linux Micro 6.2	kubevirt	before 1.7.0-160000.1.1	1.7.0-160000.1.1

Same product

kubevirt: all records

Other highest-scoring records for the same primary product.

CVE-2020-14316A flaw was found in kubevirt 0.29 and earlier.
39Monitor
CVE-2025-64324KubeVirt Vulnerable to Arbitrary Host File Read and Write
34Monitor
CVE-2023-26484On a compromised KubeVirt node, the virt-handler service account can be used to modify all node specs
32Monitor

Published before and after this one in the same product

← EarlierCVE-2024-33394May 2, 2024 · An issue in kubevirt kubevirt v1.2.0 and before allows a local attacker to execute arbitrary code via a crafted command to get the token com
23Monitor
← EarlierCVE-2025-64432Nov 7, 2025 · KubeVirt Affected by an Authentication Bypass in Kubernetes Aggregation Layer
18Monitor
Later →CVE-2025-64434Nov 7, 2025 · KubeVirt Improper TLS Certificate Management Handling Allows API Identity Spoofing
25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
kubevirt kubevirt	1.5.3 · description	Vendor (CNA)
azl3 kubevirt 1.5.0-5 on Azure Linux 3.0	1.5.3-2 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 kubevirt 0.59.0-31 on CBL Mariner 2.0	0.59.0-33 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 kubevirt 0.59.0-33 on CBL Mariner 2.0	0.59.0-33 · CBL-Mariner Releases	Microsoft (MSRC)
Go:kubevirt.io/kubevirt	1.5.3	Package registry (OSV)
Go:kubevirt.io/kubevirt	1.6.0-beta.0.0.20250801195231-a81b27d4600c	Package registry (OSV)
Go:kubevirt.io/kubevirt	1.6.1	Package registry (OSV)
opensuse:kubevirt	1.6.3-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
opensuse:kubevirt-1.8	1.8.3-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
opensuse:kubevirt1.8	1.8.3-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
suse:kubevirt	1.6.3-150700.3.13.1 · SUSE:Linux Enterprise Module for Containers 15 SP7	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

—

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2025-644340 days apartKubeVirt Improper TLS Certificate Management Handling Allows API Identity Spoofing
25Monitor
CVE-2025-644320 days apartKubeVirt Affected by an Authentication Bypass in Kubernetes Aggregation Layer
18Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/kubevirt/kubevirt/commit/09eafa068ec01eca0e96ebafeeb9522a878dbf64

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records