Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-38jw-g2qx-4286

KubeVirt Affected by an Authentication Bypass in Kubernetes Aggregation Layer

CVSS 4.7 MediumEPSS 0.0015 · 3rd percentile

Published by the GitHub Advisory Database at 6 Nov 2025, 23:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
kubevirt.io/kubevirtGo<1.5.3 || >=1.6.0-alpha.0, <1.6.1 || >=1.7.0-alpha.0, <1.7.0-rc.01.5.3, 1.6.1, 1.7.0-rc.0
Identifiers
GHSA-38jw-g2qx-4286 · CVE-2025-64432 · GO-2025-4103
Weakness (CWE)
CWE-287 · CWE-295
Tags
Published
6 Nov 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

GHSA-38jw-g2qx-4286 affects the Go module kubevirt.io/kubevirt before 1.5.3, from 1.6.0-alpha.0 before 1.6.1, and from 1.7.0-alpha.0 before 1.7.0-rc.0. In virt-api, the client certificate's Common Name is not validated against the allowed values from the extension-apiserver-authentication ConfigMap, so requests over mTLS can bypass RBAC. An attacker needs a certificate signed by the front-proxy CA plus network access to virt-api, such as from a pod in the cluster. Upgrade to 1.5.3, 1.6.1, 1.7.0-rc.0 or later.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.7 Medium 3.1 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0015, the 3rd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.