CVE-2024-49117 is a critical remote code execution vulnerability in Microsoft Windows Hyper-V. Based on the provided content, exploitation requires an authenticated attacker operating from within a guest virtual machine to send specially crafted file operation requests to hardware resources exposed to that VM. Successful exploitation can result in code execution on the Hyper-V host operating system and may also enable cross-VM compromise, allowing the attacker to escape the originally compromised guest and target other virtual machines on the same host.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical Hyper-V remote code execution vulnerability that could enable cross-VM compromise.
A remote code execution vulnerability in Windows Hyper-V that could allow an attacker on a guest VM to compromise other VMs on the same host.
A critical Hyper-V vulnerability that allows an authenticated guest VM user to execute code on the host OS and/or conduct cross-VM attacks.
A remote code execution vulnerability in Windows Hyper-V.
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.