Incorrect Permission Assignment for Critical Resource Affecting github.com/kubevirt/kubevirt/pkg/util/tls package, versions <1.5.3>=1.6.0-alpha.0 <1.6.1


Severity

Recommended
0.0
medium
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

Exploit Maturity
Proof of Concept
EPSS
0.01% (1st 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-GOLANG-GITHUBCOMKUBEVIRTKUBEVIRTPKGUTILTLS-13863405
  • published9 Nov 2025
  • disclosed7 Nov 2025
  • creditMihail Kirov, Sébastien Rolland

Introduced: 7 Nov 2025

NewCVE-2025-64432  (opens in a new tab)
CWE-732  (opens in a new tab)

How to fix?

Upgrade github.com/kubevirt/kubevirt/pkg/util/tls to version 1.5.3, 1.6.1 or higher.

Overview

Affected versions of this package are vulnerable to Incorrect Permission Assignment for Critical Resource due to the virt-api component failing to validate the CN field in client TLS certificates against allowed values in the extension-apiserver-authentication configmap. An attacker can bypass RBAC controls by impersonating the Kubernetes API server and its aggregator component through direct communication with the aggregated API server.

Note:

These prerequisites must be met for successful exploitation:

  1. The attacker must possess a valid front-end proxy certificate signed by the trusted CA (requestheader-client-ca-file). For example, they can steal the certificate material by compromising a front-end proxy or they could obtain a bundle by exploiting a poorly configured and managed PKI system.

  2. The attacker must have network access to the virt-api service, such as via a compromised or controlled pod within the cluster.

CVSS Base Scores

version 4.0
version 3.1