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

KubeVirt Affected by an Authentication Bypass in Kubernetes Aggregation Layer

Noroxi assessment

Priority: Monitor (action score 18/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.14% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: 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; cbl2 kubevirt 0.59.0-33 on CBL Mariner 2.0 0.59.0-33.

Low priority for now. Upgrade to 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; cbl2 kubevirt 0.59.0-33 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. 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.

MediumCVSS 4.7 · v3.1—No exploit Fix available

Published: Nov 7, 2025
Updated: Jun 17, 2026
EPSS: 0.1% · 3th percentile
CWE: CWE-287

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 18 / 40 · 4.7 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

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

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 4.7
CNA · GitHub_M: 4.7; agree

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, < 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.20250730135146-231dc69723f3	1.6.0-beta.0.0.20250730135146-231dc69723f3
Go	kubevirt.io/kubevirt	from 1.6.0-rc.0 · before 1.6.1	1.6.1
Go	kubevirt.io/kubevirt	from 1.6.2 · before 1.7.0-rc.0	1.7.0-rc.0
Go	kubevirt.io/kubevirt	from 1.7.0-alpha.0 · before 1.7.0-rc.0	1.7.0-rc.0
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
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-2022-1798Sep 15, 2022 · Path Traversal vulnerability in Kubevirt
26Monitor
← 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
Later →CVE-2025-64433Nov 7, 2025 · KubeVirt Arbitrary Container File Read
26Monitor

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
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.20250730135146-231dc69723f3	Package registry (OSV)
Go:kubevirt.io/kubevirt	1.6.1	Package registry (OSV)
Go:kubevirt.io/kubevirt	1.7.0-rc.0	Package registry (OSV)
opensuse:kubevirt	1.7.0-160000.1.1 · openSUSE:Leap 16.0	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.

CVE-2026-13208229 days apartKubevirt: virt-handler-rhel9: kubevirt: virt-handler notify server trusts vmi identity from unauthenticated grpc request body
26Monitor
CVE-2025-644340 days apartKubeVirt Improper TLS Certificate Management Handling Allows API Identity Spoofing
25Monitor

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-644330 days apartKubeVirt Arbitrary Container File Read
26Monitor

Bug bounty scope

No known public program.

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

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

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

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

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

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

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

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

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/231dc69723f331dc02f65a31ab4c3d6869f40d6a

Show all references (2 more)

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

All records