CVE-2024-20659 is a Windows Hyper-V security feature bypass vulnerability affecting systems where Hyper-V relies on UEFI-based trust protections. On specific hardware, an attacker with local or physical access can bypass UEFI security controls, which can lead to compromise of the Hyper-V hypervisor and the secure kernel. Available reporting indicates exploitation requires rebooting the affected device and is constrained to particular hardware conditions. The issue is described as a bypass of platform security protections rather than a conventional memory corruption flaw or direct remote code execution bug.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A zero-day Hyper-V security feature bypass vulnerability that can let a local attacker on specific hardware bypass UEFI protections and gain control of the hypervisor and secure kernel after a reboot.
A security feature bypass vulnerability in Windows Hyper-V that could allow an attacker to compromise the hypervisor and kernel after gaining network access.
A security feature bypass vulnerability in Windows Hyper-V.
A Hyper-V vulnerability that could defeat/bypass the secure kernel under certain conditions involving a reboot (per the content).
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.