{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46655 exists.","fix":"No fix has been published for CVE-2026-46655 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46655 is a high-severity vulnerability in virtio-win kvm-guest-drivers-windows, published on 18 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46655 and fix it if it is affected.\n\nWhat it is: CVE-2026-46655 is a high-severity vulnerability in virtio-win kvm-guest-drivers-windows, published on 18 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46655 exists.\n\nAffected product: virtio-win kvm-guest-drivers-windows. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-46655/ (Markdown: https://insights.sbomify.com/CVE-2026-46655/index.md)","id":"CVE-2026-46655","markdown":"https://insights.sbomify.com/CVE-2026-46655/index.md","name":"CVE-2026-46655","record":{"aliases":["GHSA-qrhp-4mhp-hjwh"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows virtio drivers","requires_auth":"low_privilege","summary":"A local attacker can exploit an integer overflow in the Viosock driver to corrupt kernel memory and escalate privileges on Windows guests.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"virtio-win provides Windows paravirtualized drivers for QEMU and KVM. From mm210 until mm320, the Viosock driver permits a low-privilege local process to submit an IOCTL_SELECT request with attacker-controlled VIRTIO_VSOCK_SELECT.Fdss[*].fd_count values that overflow the 32-bit sum used by VIOSockSelect for bounds checking. The wrapped sum can pass the FD_SETSIZE check even though an individual descriptor count is much larger than the expected limit. VIOSockSelectCopyFds then iterates using the unchecked count and writes beyond the allocated pPkt-\u003eFds array in the NonPagedPool kernel heap. Successful exploitation can corrupt kernel memory and enable privilege escalation in a Windows guest running the driver. This issue is fixed in mm320.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"virtio-win: Integer overflow causing a heap overflow in Viosock driver","id":"CVE-2026-46655","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Bludit CMS has improper authorization and mediation failure leading to persistent ghost sessions","id":"CVE-2026-46656"},"packages":[],"prev":{"headline":"Plonky3 MultiField32Challenger: transcript malleability and challenge entropy loss","id":"CVE-2026-46654"},"products":["kvm-guest-drivers-windows"],"published":"2026-09-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-23","vendors":["virtio-win"]},"summary":"A local attacker can exploit an integer overflow in the Viosock driver to corrupt kernel memory and escalate privileges on Windows guests.","url":"https://insights.sbomify.com/CVE-2026-46655/"}