# KubeVirt Affected by an Authentication Bypass in Kubernetes Aggregation Layer Advisory record · `GHSA-38jw-g2qx-4286` - **Identifiers:** `GHSA-38jw-g2qx-4286` · `CVE-2025-64432` · `GO-2025-4103` - **State:** Confirmed - **Severity:** CVSS 4.7 Medium - **Critical:** No - **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html) · [CWE-295](https://cwe.mitre.org/data/definitions/295.html) - **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md) - **Published:** 6 Nov 2025 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No 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. ## Affected packages - `kubevirt.io/kubevirt` (Go): affected `<1.5.3 || >=1.6.0-alpha.0, <1.6.1 || >=1.7.0-alpha.0, <1.7.0-rc.0`; fixed in `1.5.3`, `1.6.1`, `1.7.0-rc.0` ## 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 - 4.7 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`, from 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 - 31 Oct 2026, 14:14 UTC: First seen by agentprime - 31 Oct 2026, 14:14 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-38jw-g2qx-4286) ## Sources - [GitHub Advisory Database: GHSA-38jw-g2qx-4286](https://github.com/advisories/GHSA-38jw-g2qx-4286) - [OSV: GHSA-38jw-g2qx-4286](https://osv.dev/vulnerability/GHSA-38jw-g2qx-4286) - - - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .