CVSS 3.1
7.8 highCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (7.8) in virtio-win kvm-guest-drivers-windows. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-46655 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-46655?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-46655?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-46655 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| virtio-win kvm-guest-drivers-windows | >= mm210, < mm320 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Red Hat | enterprise_linux:9::appstream | virtio-win | 0:1.9.58-0.el9_4 | RHBA-2026:56986 |
| Red Hat | enterprise_linux:9::appstream | virtio-win | 0:1.9.61-0.el9_8 | RHBA-2026:70252 |
| Red Hat | enterprise_linux:10.2 | virtio-win | 0:1.9.58-0.el10_2 | RHBA-2026:43594 |
| Red Hat | enterprise_linux_eus:10.0 | virtio-win | 0:1.9.58-0.el10_0 | RHBA-2026:65134 |
| Red Hat | rhel_e4s:9.2::appstream | virtio-win | 0:1.9.58-0.el9_2 | RHBA-2026:65127 |
| Red Hat | rhel_eus:9.6::appstream | virtio-win | 0:1.9.58-0.el9_6 | RHBA-2026:65128 |
From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat.
Red Hat rates this Important.
This flaw requires local access to a Windows guest with the virtio-vsock driver installed. The following steps reduce exposure:
1. Disable the viosock driver on guests that do not need VM socket communication. Stop the viosock service and set its startup type to Disabled. This eliminates the attack surface entirely and is the strongest interim mitigation.
2. Verify memory protections are active in the guest. These raise the cost of exploiting the heap overflow significantly.
3. Minimize guest-to-host attack surface on the hypervisor. Even a full guest kernel compromise is contained by the KVM boundary. Disable unnecessary virtio devices and limit PCI passthrough to reduce the risk of chaining with a separate host escape.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | virtio-win-0:1.9.58-0.el10_2 | Fixed 2026-07-22 | RHBA-2026:43594 |
| Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions | virtio-win-0:1.9.58-0.el9_2 | Fixed 2026-09-08 | RHBA-2026:65127 |
| Red Hat Enterprise Linux 9.6 Extended Update Support | virtio-win-0:1.9.58-0.el9_6 | Fixed 2026-09-08 | RHBA-2026:65128 |
| Red Hat Enterprise Linux 8 | virtio-win | Will not fix | |
| Red Hat Enterprise Linux 9 | virtio-win | Affected | |
| Red Hat OpenShift Virtualization 4 | container-native-virtualization/virtio-win | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-46655.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.