CVE-2022-21894
🟠MediumMicrosoft Windows Boot Manager / Secure Boot — Windows 10, Windows 11, Server 2012 through Server 2022 (20 product rows in the record) · Builds before the 11/01/2022 update ; fixed builds include Windows 11 21H2 → 22000.434, Windows 10 21H2 → 19044.1466, Server 2022 → 20348.469, Server 2012 → 6.2.9200.23584
CVSS (Koffei note)
4.4CVSS (v3.1, CVE List)
4.4EPSS (2026-11-18)
9.116%95.41th percentile
Exploitation
Yes — historically. Abused by the BlackLotus UEFI bootkit (ESET, 01/03/2023), sold as malware-as-a-service from at least 06/10/2022, with a public PoC circulating since August 2022. CISA-ADP SSVC still reads exploitation active (timestamp 01/03/2023, container updated 07/09/2024) while Microsoft's own vector still carries
E:U (exploit unproven) — a standing contradiction between the two. No 2025 or 2026 exploitation reporting was found ; no kev block in the record. The AV:L/PR:H metrics are the giveaway: this is post-compromise persistence and defence evasion, not initial accessTimeline
- 11/01/2022CVE record published (CVE List)
- 26/10/2026APT41-linked "BlackX" UEFI bootkit bypasses Secure Boot via an expired-but-unrevoked certificate
Relationships
exploits suspected named in the same story vendor · Select a box to open its page · All relationships
Risk
4.4 Medium (v3.1, Microsoft CNA) — AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N/E:U/RL:O/RC:C, EPSS 6.768% (93.9th percentile) (CWE-863 : "baton drop" — the
truncatememory BCD option strips the serialized Secure Boot policy out of memory, unlocking nointegritychecks and testsigning ; a vulnerable hvloader.efi then loads a self-signed mcupdate_*.dll, giving code execution before ExitBootServices, after which a MokList key plus a Microsoft-signed shim persist without re-exploiting each boot)Fix
Partly — the code fix shipped 11/01/2022 (KB5009566, KB5009543, KB5009557, KB5009545, KB5009546, KB5009585, KB5009555, KB5009595, KB5009619), but the vulnerable signed boot binaries were never revoked in DBX, so an attacker with administrator rights can bring their own copy to a fully patched host — the NSA warned of a "false sense of security". Revocation lives in KB5025885, which is formally the CVE-2023-24932 mitigation, so baton drop's actual closure is tracked under a different CVE: per Microsoft's page of 30/09/2026 those mitigations are not enabled by default, need manual registry and scheduled-task steps to add "Windows Production PCA 2011" to DBX, are irreversible while Secure Boot stays on, and the Enforcement Phase still has no announced date
Official description
Secure Boot Security Feature Bypass Vulnerability
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N/E:U/RL:O/RC:C