# KubeVirt Vulnerable to Arbitrary Host File Read and Write Advisory record · `GHSA-46xp-26xh-hpqh` - **Identifiers:** `GHSA-46xp-26xh-hpqh` · `CVE-2025-64324` · `GO-2025-4110` - **State:** Confirmed - **Severity:** CVSS 8.5 High - **Critical:** No - **Weakness (CWE):** [CWE-123](https://cwe.mitre.org/data/definitions/123.html) · [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-732](https://cwe.mitre.org/data/definitions/732.html) - **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [CWE-123](https://agentprime.io/advisories/tag/cwe-123.md) - **Published:** 7 Nov 2025 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 7 Nov 2025, 18:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `kubevirt.io/kubevirt` (Go): affected `<1.6.1 || >=1.7.0-alpha.0, <1.7.0-rc.0`; fixed in `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. > KubeVirt versions before 1.6.1, and from 1.7.0-alpha.0 up to but not including 1.7.0-rc.0, are vulnerable. An attacker who can create a VM that uses the hostDisk feature with the DiskOrCreate option (the hostDisk feature gate must be enabled) can get existing host files owned by more privileged users re-owned to the qemu user, letting the VM read and modify them. Upgrade to KubeVirt 1.6.1 or 1.7.0-rc.0. The source gives no workaround. 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 - 8.5 High, CVSS 4.0: `CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0024, the 15th percentile, on 5 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-46xp-26xh-hpqh) ## Sources - [GitHub Advisory Database: GHSA-46xp-26xh-hpqh](https://github.com/advisories/GHSA-46xp-26xh-hpqh) - [OSV: GHSA-46xp-26xh-hpqh](https://osv.dev/vulnerability/GHSA-46xp-26xh-hpqh) - - - - - - 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: .