CVE-2022-21894General(microsoft / windows_10)

CRITICALCVSS 4.4 · MEDIUM

Exploitation ongoing with high activity in latest observed window (1 mentions)

Immediate actions

  • Patch microsoft windows_10 systems immediately
  • Assume compromise if assets are exposed
  • Hunt for exploitation attempts and persistence artifacts
  • Increase monitoring for publicly documented tradecraft

Recommended action window: Immediate (within 24h)

NVD description

Secure Boot Security Feature Bypass Vulnerability

8.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-863

Priority

CRITICAL

Exploitation

ACTIVE

PoC

YES

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • windows_10
  • windows_11
  • windows_8.1
  • windows_server

Threat summary

  • Active exploitation appears in 1 classified signals
  • Public PoC and exploit tooling are both present
  • Patch or workaround signal is available
  • 4 mentions across 4 observed days

What's happening

  • Active exploitation reported across 1 signal
  • Exploit tool or code specified in 1 signal
  • PoC mentioned or linked in 1 signal
  • Patch or workaround mentioned in 2 signals
  • Technical details provided in 1 signal
  • General: 2 classified signals
  • Peaked 3d ago at 1 mentions (2026-04-09); latest day: 1
  • 4 total mentions across 4 days

Affected systems

Vendors
Products
windows_10windows_11windows_8.1windows_serverwindows_server_2012windows_server_2016windows_server_2019

9 versions affected across 7 products

Deep dive

Activity timeline4 mentions / 4d
00111Mentions · 2026-04-09: 1Mentions · 2026-05-07: 1Mentions · 2026-07-17: 1Mentions · 2026-08-11: 1PoC Mentioned / Linked · 2026-07-17: 1Exploit Tool / Code · 2026-07-17: 1Active Exploitation · 2026-07-17: 1Patch / Workaround · 2026-07-17: 1Patch / Workaround · 2026-08-11: 1Technical Details · 2026-07-17: 104-0905-0707-1708-11
Signal classification3 categories
General
250.0%
Active Exploitation
125.0%
Patch
125.0%
Referenced assets2 URLs
Classification over time
DateTotalLabels
2026-04-091
General1
2026-05-071
General1
2026-07-171
Active Exploitation1
2026-08-111
Patch1
Full discourse4 posts
  • cr3ghost@cr3ghost
    Active Exploitation

    Microsoft patched CVE-2022-21894 in January 2022. The vulnerable binaries were never revoked from the UEFI revocation list. Over a year later, BlackLotus used those same signed binaries to bypass Secure Boot on fully updated Windows 11 systems. 80KB. $5,000 on underground forums. Disables HVCI via a single registry write. Suspends BitLocker programmatically. Patches Windows Defender out of memory at boot. Enrolls its own MOK key through a legitimate Microsoft-signed shim. Kernel driver triggers BSOD if you try to remove its files. A patch that never revoked the vulnerable binaries was never really a patch. Understanding this attack chain matters for anyone working in malware analysis, threat intelligence, or detection engineering. If your threat model assumes Secure Boot protects you, read this. https://www.welivesecurity.com/2023/03/01/blacklotus-uefi-bootkit-myth-confirmed/ Author: @ESETresearch #Malware #ThreatIntel #InfoSec

    Post summary

    Microsoft patched CVE‑2022‑21894 but failed to revoke the vulnerable binaries, allowing BlackLotus to exploit them on fully updated Windows 11 machines by bypassing Secure Boot, disabling HVCI and BitLocker, and deploying a kernel driver that forces a BSOD.

    011056283.9K
    7.8K followersView on X
  • Patch My PC@PatchMyPC
    General

    This is where teams get stuck ⬇️ IT: “We’ve handled it.” Security: “Can you prove it?” IT: “...we think so?” Devices run. Reports look clean. That doesn’t mean you’re covered 👀 CVE-2022-21894 can still exist quietly. Save your spot for April 29th 🗓️ https://bit.ly/4sHDU6y #MSIntune #Reporting

    Post summary

    The tweet highlights that CVE‑2022‑21894 may still exist in environments and urges teams to verify coverage rather than rely on clean reports.

    01071494
    8.2K followersView on X
  • 𝖊𝖝𝖆𝖊𝖊𝖙𝖍 (𑀲𑀓𑁆𑀬𑀫𑀼𑀦𑀻)@EXAEETH
    Patch

    Integralność firmware: cykliczne sprawdzanie obrazu BIOS/UEFI za pomocą CHIPSEC lub vendorowych narzędzi. Częste aktualizacje BIOS/UEFI (łatki bezpieczeństwa) zapobiegają exploity (np. łatki MS do CVE-2022-21894). Monitorowanie stanu sprzętu – oprogramowanie porównuje nowe firmware z zaufanym artefaktem (np. skanowanie GV-D files). Dodatkowe środki: włączenie BIOS Lock i SMRAM Lock, wyłączanie dostępu do NVRAM przez OS (jeśli sprzęt pozwala).

    Post summary

    The text outlines firmware integrity checks and recommends patching, specifically citing security updates for CVE‑2022‑21894, without evidence of exploits or PoC.

    0000025
    242 followersView on X
  • Томас Рисов@TomasRisov
    General

    CVE-2022-21894 CVE-2024-36877..... drum roll CVE-2026-31431 !!!

    Post summary

    The post merely lists three CVE identifiers without providing additional context or actionable information.

    0000058
    142 followersView on X
CPE platform detail29 entries

29 of 29 entries

PartVendorProductVersionTarget SWTarget HW
OSmicrosoftwindows_10--x64
OSmicrosoftwindows_10--x86
OSmicrosoftwindows_101607-x64
OSmicrosoftwindows_101607-x86
OSmicrosoftwindows_101809-arm64
OSmicrosoftwindows_101809-x64
OSmicrosoftwindows_101809-x86
OSmicrosoftwindows_101909-arm64
OSmicrosoftwindows_101909-x64
OSmicrosoftwindows_101909-x86
OSmicrosoftwindows_1020h2-arm64
OSmicrosoftwindows_1020h2-x64
OSmicrosoftwindows_1020h2-x86
OSmicrosoftwindows_1021h1-arm64
OSmicrosoftwindows_1021h1-x64
OSmicrosoftwindows_1021h1-x86
OSmicrosoftwindows_1021h2-arm64
OSmicrosoftwindows_1021h2-x64
OSmicrosoftwindows_1021h2-x86
OSmicrosoftwindows_11--arm64
OSmicrosoftwindows_11--x64
OSmicrosoftwindows_8.1---
OSmicrosoftwindows_8.1---
OSmicrosoftwindows_server2022--
OSmicrosoftwindows_server20h2--
OSmicrosoftwindows_server_2012---
OSmicrosoftwindows_server_2012r2--
OSmicrosoftwindows_server_2016---
OSmicrosoftwindows_server_2019---

Explore more