Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2024-21407: Windows Hyper-V Guest-to-Host Remote Code Execution

Published Mar 12, 2024 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.1High · v3.1
EPSS16.3%97th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Microsoft Corporation
IdentifiersCVE-2024-21407CWE-20

CVE-2024-21407 is a remote code execution vulnerability in Windows Hyper-V that permits escape from a guest virtual machine to its host. An authenticated attacker on a guest VM can send specially crafted file operation requests to virtual-machine hardware resources, potentially causing code execution on the Hyper-V host. Exploitation requires gathering environment-specific information and performing preparatory work. Microsoft released fixes in March 2024 for every supported Windows version.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can breach the guest-to-host isolation boundary and execute attacker-controlled code on the Hyper-V host. Host compromise could also enable manipulation of other guest operating systems running on the same server.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by limiting untrusted or lower-trust workloads on Hyper-V hosts, restricting who can obtain code execution or authenticated access within guest VMs, and segregating sensitive workloads from potentially attacker-controlled tenants or virtual machines. Minimize opportunities for guest-to-host interaction involving exposed hardware resources until vendor fixes are deployed. Vendor-provided security updates are the primary mitigation.

Remediation

Patch, then assume compromise.

Apply the Microsoft March 12, 2024 security update addressing CVE-2024-21407 for the installed Windows or Windows Server version. Fixes were released for every Windows version supported at that time.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
YellowKey-Bitlocker-CVE-2026-45585This repository is a Windows C++ utility named YellowKey that presents itself as a BitLocker recovery key extractor and CVE-2026-45585 bypass assessment tool. It is not a remote exploit; it is a local/physical-access post-compromise or audit-style tool focused on BitLocker-protected systems. The core capability is sensitive: it enumerates BitLocker volumes via WMI, invokes manage-bde to retrieve protector details and parse numerical recovery passwords, tests whether a drive uses a TPM-only protector set, inspects TPM presence/status through TBS APIs, verifies installed KB patches, and exports audit reports that may contain full recovery keys. Repository structure is organized into config/, docs/, include/, modules/, and src/. The config directory contains CLI syntax, CVE metadata, protector heuristics, report templates, and runtime settings. The docs directory provides installation, remediation, troubleshooting, and CVE background. The include directory defines interfaces for BitLocker, TPM, parsing, reporting, and app control. The src directory contains the main entry point and implementations for BitLocker API access, CLI handling, GUI, key parsing, reporting, and TPM interaction. The modules directory adds operational features such as bypass testing, event logging, patch verification, remediation guidance, silent export, and volume management. Main execution starts in src/main.cpp, which selects GUI or CLI mode based on --cli. CLI commands include scan, extract, bypass-test, tpm-status, export, and remediation. The most important code paths are BitLockerAPI::EnumerateVolumes() using WMI namespace ROOT\\CIMV2\\Security\\MicrosoftVolumeEncryption and query SELECT * FROM Win32_EncryptableVolume; BitLockerAPI::GetRecoveryKey() and GetProtectorTypes() invoking manage-bde -protectors -get; KeyParser routines extracting numerical passwords and protector types; BypassTester logic marking TPM-without-PIN/StartupKey as vulnerable; and VolumeManager::UnlockVolume() invoking manage-bde -unlock with a recovery password. From an exploit-intelligence perspective, the repository’s practical capability is recovery-key disclosure and local BitLocker access assistance rather than a full autonomous exploit chain. It can expose or export recovery keys, determine whether a host is configured in a supposedly vulnerable way, and use a provided recovery key to unlock a volume. The code contains several implementation inconsistencies and simplifications, but the intent and offensive utility are clear enough to classify it as an operational local BitLocker key extraction/audit tool rather than a mere detector.yellowkeycve · Disclosed Aug 11, 2026 · cpp · c++ · local · physicalOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 21h2operating_system
Microsoft CorporationWindows 11 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 23h2operating_system
FAQ

Frequently asked questions

Is CVE-2024-21407 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2024-21407?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2024-21407, the earliest disclosed Aug 11, 2026.
Is there a patch for CVE-2024-21407?
Apply the Microsoft March 12, 2024 security update addressing CVE-2024-21407 for the installed Windows or Windows Server version. Fixes were released for every Windows version supported at that time.
What products are affected by CVE-2024-21407?
Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, and 10 more.
How severe is CVE-2024-21407?
CVE-2024-21407 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 16.3% (97th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.