Skip to main content
Mallory
MediumExploited in the wildPublic exploitVulnerability

CVE-2023-24932: Secure Boot Bypass in Microsoft Windows Boot Manager

Published May 9, 2023 · Updated 8 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days12 mentions · peak 5 in a dayToday
CVSS6.7Medium · v3.1
EPSS11.8%96th percentile
CISA KEVNoNot listed
In the wildActivePer CISA SSVC
Vendor
Microsoft Corporation
IdentifiersCVE-2023-24932CWE-693

CVE-2023-24932 is a Secure Boot security feature bypass vulnerability in Microsoft Windows Boot Manager associated with the BlackLotus UEFI bootkit. An attacker with administrative privileges or physical access can install an affected boot policy and bypass Secure Boot, allowing untrusted software to execute during startup. The vulnerability undermines the trusted boot chain on Windows devices with Secure Boot enabled. Microsoft initially addressed it in May 2023, with subsequent updates expanding the protections and boot-manager revocations. Installing Windows updates alone does not necessarily activate the required protections.

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 compromises boot-chain integrity and enables malicious code to execute before Windows and many endpoint security controls initialize. Bootkit deployment can support persistent control, concealment, security-tool interference, and subsequent kernel or user-mode payload execution, with potentially high confidentiality, integrity, and availability impacts. This is a post-compromise or physical-access attack, not an unauthenticated remote entry point. Suspected exploitation in FishMonger activity remains unconfirmed.

Mitigation

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

Before enabling revocations, test representative hardware and virtual-machine configurations, install required OEM firmware updates, retain BitLocker recovery keys, and update installation, recovery, removable, and network boot media to compatible boot components. Update every Windows installation on multiboot systems before applying revocations. Apply the new trust anchors and updated boot managers before revoking older certificates; incorrect sequencing can leave devices unbootable. Verify effective DBX and rollback-protection state after deployment. Restrict administrative privileges and unauthorized physical or hypervisor access to reduce opportunities for installation. Certificate expiration alone does not block vulnerable boot components.

Remediation

Patch, then assume compromise.

Install the latest applicable Windows security updates on all supported devices, including the protections delivered in the July 8, 2025 updates or their successors, and explicitly activate the protections following Microsoft's current KB5025885 procedure. Deployment includes establishing trust in the 2023 Secure Boot certificates, installing Windows Boot Manager signed by Windows UEFI CA 2023, revoking Windows Production PCA 2011 through the firmware Forbidden Signature Database (DBX), and applying the applicable firmware-backed Secure Version Number rollback protection. Verify successful deployment in firmware and Windows servicing events rather than relying solely on installed-update status. These protections are preventive and do not remove an existing bootkit compromise.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 4 rejected by Mallory's analysis as not a working exploit.

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 20h2operating_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 11 24h2operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2008 R2operating_system
Microsoft CorporationWindows Server 2008 Sp2operating_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 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system
FAQ

Frequently asked questions

Is CVE-2023-24932 exploited in the wild?
Yes. As of Nov 10, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2023-24932?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2023-24932, the earliest disclosed Aug 11, 2026.
Is there a patch for CVE-2023-24932?
Install the latest applicable Windows security updates on all supported devices, including the protections delivered in the July 8, 2025 updates or their successors, and explicitly activate the protections following Microsoft's current KB5025885 procedure. Deployment includes establishing trust in the 2023 Secure Boot certificates, installing Windows Boot Manager signed by Windows UEFI CA 2023, revoking Windows Production PCA 2011 through the firmware Forbidden Signature Database (DBX), and applying the applicable firmware-backed Secure Version Number rollback protection.
What products are affected by CVE-2023-24932?
Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 20h2, Microsoft Corporation Windows 10 21h2, and at least 15 more.
How severe is CVE-2023-24932?
CVE-2023-24932 has a CVSS v3.1 score of 6.7 (Medium) and an EPSS score of 11.8% (96th percentile) as of Nov 10, 2026.
Activity feed

Recent activity

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

View more in app →
the hacker newsNews · Oct 23, 2026BlackX UEFI Bootkit Bypasses Secure Boot on Patched Windows Systems Missing RevocationsA security-feature bypass vulnerability linked to BlackLotus. The article cites limited indications that some versions of the SprySOCKS backdoor used by FishMonger may contain a UEFI bootkit component likely exploiting this flaw. This is supporting context for possible links between FishMonger and BlackX, not confirmation that BlackX exploits this CVE.Read more ↗cryptika blogNews · Oct 23, 2026Hackers Use New BlackX Bootkit to Bypass Windows Secure Boot on Fully Patched Systems | Cryptika CybersecurityReferenced as the subject of Microsoft's Secure Boot protection deployment guidance. The article uses this guidance to explain why installing Windows updates alone may not activate all required protections, and why administrators must verify revocations and test boot and recovery compatibility. It does not state that BlackX exploits this vulnerability.Read more ↗cyber security newsNews · Oct 23, 2026Hackers Use New BlackX Bootkit to Bypass Windows Secure Boot on Fully Patched SystemsA Windows Secure Boot vulnerability referenced through Microsoft's protection-deployment guidance to explain why installed updates alone may not activate all boot protections. The article describes certificate, boot-manager, and UEFI revocation-list updates, with compatibility testing and recovery preparation before deployment. It does not state that BlackX exploits this CVE.Read more ↗malware newsNews · Oct 22, 2026How APT41 revived the BlackLotus bootkit to attack diplomatic organizations in Central Asia - Malware News - Malware Analysis, News and IndicatorsMentioned as a vulnerability potentially exploited by an unspecified UEFI bootkit in an earlier report about FishMonger. The article hypothesizes that this bootkit was BlackX, based on a shared identifier, but does not confirm exploitation of this CVE. Its own BlackX analysis identifies Baton Drop as the exploited vulnerability.Read more ↗
+22 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 evidence7Every report linking this CVE to a named adversary.
Associated malware22Malware 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 activity14Community discussion across Reddit, Mastodon, and other social sources.