Skip to main content
Mallory
MediumExploited in the wildPublic exploitVulnerability

CVE-2022-21894: Baton Drop

Published Jan 11, 2022 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days39 mentions · peak 10 in a dayToday
CVSS4.4Medium · v3.1
EPSS9.1%95th percentile
CISA KEVNoNot listed
In the wildActivePer CISA SSVC
Vendor
Microsoft Corporation
IdentifiersCVE-2022-21894CWE-693
Also known asblacklotus

Baton Drop is a Secure Boot bypass vulnerability in the Windows UEFI boot manager. A logic flaw allows attackers to break the startup chain of trust and execute attacker-controlled EFI code before Windows security defenses initialize. BlackLotus and BlackX exploit the vulnerability as part of bootkit installation chains that enroll attacker-controlled Machine Owner Keys and establish persistence in the EFI System Partition. Microsoft patched the underlying vulnerability in 2022, but older, legitimately signed vulnerable boot managers can remain exploitable on updated systems when the necessary Secure Boot revocations have not been applied.

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 undermines boot integrity, allowing unauthorized code to execute before the operating system and many security controls become active. Bootkits leveraging the bypass can establish boot-level persistence, load malicious kernel drivers, interfere with endpoint protection, and deploy espionage payloads. BitLocker encryption-key extraction is possible under certain conditions, although the specific prerequisites are not established. This vulnerability is a post-compromise persistence and defense-evasion mechanism rather than an initial-access vector.

Mitigation

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

Restrict administrative privileges and physical access, protect privileged credentials, and maintain current endpoint protection to reduce opportunities for bootkit deployment. Where unnecessary for the device's boot configuration, removing the Microsoft 3rd Party UEFI CA can block the documented BlackLotus chain, but does not eliminate CVE-2022-21894. Monitor unexpected Machine Owner Key enrollment, EFI System Partition changes, boot configuration and Measured Boot discrepancies, and signs of security-monitoring tampering.

Remediation

Patch, then assume compromise.

Install applicable Microsoft security updates addressing CVE-2022-21894 and complete the supported Secure Boot revocation procedures that prevent older vulnerable boot managers from remaining trusted. Follow Microsoft's current deployment guidance, including KB5025885 for related BlackLotus rollback protections: provision the replacement trust certificates and updated boot manager before revoking Windows Production PCA 2011, and apply supported rollback protections. Verify that revocations are effective in the firmware DBX rather than relying solely on Windows update status or certificate expiration. Test representative hardware, update recovery and network-boot media, retain BitLocker recovery keys, and address firmware compatibility requirements before broad deployment. For confirmed BlackLotus infection, isolate the device and reformat both the operating-system and EFI partitions or restore a known-clean backup that includes the EFI partition; preventive updates alone do not remove an existing bootkit.

Public exploits

Exploits

4 exploits validated by Mallory's analysis.

View more in app →
batondrop_armv7This repository contains a multi-stage exploit chain ('baton drop') targeting ARMv7-based Windows RT devices (specifically MSM8960, e.g., Dell XPS 10). The exploit enables execution of unsigned EFI boot applications by bypassing Secure Boot and code integrity mechanisms. The structure includes C source files for three main components: boot.c (a simple EFI application), mcupdate.c (the initial loader and orchestrator), and stage2.c (the second-stage loader that prepares the environment and executes the payload). Several batch scripts automate building and signing the components. The exploit works by patching the boot process to load mcupdate.dll, which then loads stage2.dll and a user-supplied boot.efi from the EFI system partition. The README provides detailed exploitation steps and device requirements. The attack vector is local, requiring physical access and a prepared USB device. The main fingerprintable endpoints are the file paths used for loading the payload and stage2 components. The exploit is operational, providing a working method to run arbitrary code at boot on affected devices.Wack0 · Disclosed Mar 11, 2023 · c · batch · localOperationalCVE-2022-21894-Payload-NewThis repository contains an operational exploit payload for CVE-2022-21894, a Secure Boot Security Feature Bypass vulnerability affecting Microsoft Windows. The main exploit logic is implemented in 'main.c', which contains code to map and execute a custom EFI application (embedded as a byte array) in the firmware context. The build process (via 'build.bat') signs the malicious DLL and EFI binaries and renames them to mimic legitimate system files (e.g., 'mcupdate_GenuineIntel.dll', 'mcupdate_AuthenticAMD.dll', 'hello.efi'). The exploit demonstrates how an attacker can bypass Secure Boot and execute arbitrary code at the firmware level, enabling further attacks such as persistence or disabling security features. The repository is structured as a Visual Studio C/C++ project, with supporting solution and project files, and a batch script for building and signing the payloads. The exploit is not part of a framework and is a standalone operational PoC with a real payload.nova-master · Disclosed Sep 26, 2023 · c · batch · localOperationalCVE-2022-21894This repository provides a proof-of-concept (POC) exploit for CVE-2022-21894 ("Baton Drop"), a Secure Boot security feature bypass vulnerability in Microsoft Windows. The exploit leverages manipulation of boot configuration data (BCD) elements such as 'truncatememory' and 'avoidlowmemory' to remove the serialized Secure Boot policy from memory, allowing the use of dangerous boot options and the loading of self-signed payloads during the boot process. The included payload (mcupdate.c) is a simple DLL that demonstrates code execution by entering an infinite wait state, but the mechanism allows for more advanced payloads, such as those that could extract BitLocker keys. The repository also includes a tool (FveAddMetadataForPolicy.c) for manipulating BitLocker metadata, which can assist in setting up the attack. The exploit targets Windows systems with Secure Boot enabled and requires the attacker to supply custom boot applications and payloads. The code is written in C and batch scripts, and the repository is structured with separate directories for payloads and tools. No network endpoints are present; the attack is local and requires physical or privileged access to the target system.Wack0 · Disclosed Aug 9, 2022 · c · batch · localPoCCVE-2022-21894-PayloadThis repository contains a proof-of-concept (PoC) exploit payload for CVE-2022-21894, a Windows vulnerability that allows attackers to execute arbitrary code in the firmware context during the boot process. The main code file, 'main.c', implements a DLL entry point (McUpdateEntry) that, when loaded as a malicious mcupdate_*.dll, locates the Windows boot loader in memory, allocates a buffer for a custom EFI application, copies the application into memory, and executes it in the firmware context. The payload is minimal (just a stub EFI application), but the structure demonstrates how an attacker could leverage the vulnerability to run arbitrary EFI code and call EFI services. The repository is structured as a Visual Studio C/C++ project, with supporting solution and project files, and a readme describing its purpose. No network or remote endpoints are present; the attack is local and requires the ability to place a malicious DLL on the target system.ASkyeye · Disclosed Aug 18, 2022 · c · localPoC
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 10operating_system
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 1909operating_system
Microsoft CorporationWindows 10 20h2operating_system
Microsoft CorporationWindows 10 21h1operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 11operating_system
Microsoft CorporationWindows 11 21h2operating_system
Microsoft CorporationWindows 8.1operating_system
Microsoft CorporationWindows Serverapplication
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 20h2operating_system
FAQ

Frequently asked questions

Is CVE-2022-21894 exploited in the wild?
Yes. As of Nov 17, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2022-21894?
Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2022-21894, the earliest disclosed Aug 9, 2022.
Is there a patch for CVE-2022-21894?
Install applicable Microsoft security updates addressing CVE-2022-21894 and complete the supported Secure Boot revocation procedures that prevent older vulnerable boot managers from remaining trusted. Follow Microsoft's current deployment guidance, including KB5025885 for related BlackLotus rollback protections: provision the replacement trust certificates and updated boot manager before revoking Windows Production PCA 2011, and apply supported rollback protections.
What products are affected by CVE-2022-21894?
Microsoft Corporation Windows 10, Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 1909, and 13 more.
How severe is CVE-2022-21894?
CVE-2022-21894 has a CVSS v3.1 score of 4.4 (Medium) and an EPSS score of 9.1% (95th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

70 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
arstechnica securityNews · Nov 3, 2026UEFI bootkit infected fully patched Windows machines. Is Microsoft to blame? - Ars TechnicaA Windows boot manager logic flaw that enables Secure Boot bypass and, under certain conditions, extraction of BitLocker encryption keys. BlackLotus and BlackX exploit it to execute malicious code during boot. Microsoft patched the flaw in 2022, but older vulnerable boot managers initially remained trusted, allowing BlackLotus to exploit that gap and load a malicious kernel-mode driver. Additional certificate-related updates followed in 2023 and 2024; the article states that BlackX victims had installed these updates.Read more ↗xakepNews · Oct 27, 2026UEFI-буткит BlackX использует уязвимость Baton Drop для обхода Secure Boot - ХакерA Secure Boot bypass vulnerability exploited by the BlackX and BlackLotus UEFI bootkits. The reported BlackX campaign targeted diplomatic organizations in Tajikistan, Uzbekistan, and Turkmenistan after attackers obtained initial access and administrator privileges. Exploitation enables attacker-controlled EFI files to load, supporting pre-OS persistence, security-tool interference, and espionage payload deployment. Fully updated Windows systems remained exploitable because administrators had not manually activated the required certificate revocation protection. Attribution of the BlackX campaign to APT41 is assessed with medium confidence.Read more ↗cyber security newsNews · Oct 27, 2026Hackers Revive BlackLotus Techniques to Bypass Windows Secure Boot and Deploy MalwareA Windows Secure Boot vulnerability exploited by the BlackX bootkit in espionage attacks against diplomatic organizations in Tajikistan, Uzbekistan, and Turkmenistan in early 2026. After obtaining administrator privileges, attackers exploit trusted, vulnerable boot components to install custom Machine Owner Keys and load attacker-controlled EFI files. Fully patched systems remained exposed when required boot-trust revocations had not been activated. Researchers attributed the campaign to APT41 with medium confidence; attribution remains unconfirmed.Read more ↗cryptika blogNews · Oct 27, 2026Hackers Revive BlackLotus Techniques to Bypass Windows Secure Boot and Deploy Malware | Cryptika CybersecurityA Windows Secure Boot bypass vulnerability exploited by the BlackX bootkit in espionage attacks against diplomatic organizations in Tajikistan, Uzbekistan, and Turkmenistan in early 2026. After obtaining administrator privileges, attackers exploit vulnerable trusted boot components to install custom Machine Owner Keys and load attacker-controlled EFI files. Fully patched systems remained exposed because required boot-trust revocations had not been activated. Investigators attributed the campaign to APT41 with medium confidence, not confirmation.Read more ↗
+37 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 evidence13Every report linking this CVE to a named adversary.
Associated malware48Malware 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 activity29Community discussion across Reddit, Mastodon, and other social sources.