Microsoft Windows 10 Version 1809: security flaw reported in attacks
OFFICIAL NAME: Secure Boot Security Feature Bypass Vulnerability
WHAT IT IS · COMPUTERS, PHONES AND BROWSERSIt runs on staff computers, phones or browsers.
DO THIS FIRSTInstall the latest updates on every device, and turn on automatic updates. Not sure if you use it? Send this page to your IT provider or security lead and ask.
TECHNICAL SUMMARY Secure Boot Security Feature Bypass Vulnerability
WHY THIS VERDICT Attacks are confirmed, but the vulnerability is more than a year old and we see no ransomware use, public attack tools, internet-facing product, critical severity or high prediction score. Check whether it applies to you.
WHY IT RANKS HERE Exploitation is confirmed by an authoritative source. The first report is 20 days old. 12 products are affected.
- HIGHEST CONFIRMED RUNG
- EXPLOITED
- CISA KEV
- NOT YET
- EXPLOIT CODE
- PROOF OF CONCEPT CLAIMED
How far has it climbed?
01 TALK
▨ REPORTED, NOT CONFIRMEDNEWEST EVIDENCE · 1 SOURCECVE-2022-21894 discussed publicly (CIRCL sighting). CVE-2022-21894 discussed publicly (CIRCL sighting).
02 EXPOSED
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETWe have no source that counts exposed systems yet. Internet scan data needs a partnership we do not have. No evidence here does not mean nothing is exposed.
03 TRIED
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESAttacks that worked are confirmed (step 4), so attempts count as confirmed too.
04 EXPLOITED
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESExploitation of CVE-2022-21894 reported (CIRCL sighting). CISA Vulnrichment marks CVE-2022-21894 as actively exploited.
05 DAMAGE
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETBreach notices and filings rarely name the flaw that was used, so we cannot link them to this event yet. No evidence here does not mean no harm.
When each thing happened
- DISCLOSED
- EXPLOIT CODE PUBLICCLAIMED
- FIRST ATTACK REPORT
- CISA KEV LISTINGNOT YET
- US FEDERAL DEADLINENOT YET
Questions to ask this week
- Do we run Microsoft Windows 10 Version 1809? If yes, is it patched or cut off from the internet?
- Who owns fixing it, and by what date?
- Have we checked for signs of attack since the first report, not just since the patch?
How it unfolded
- Attack activity. JAN 11, 2022CISA Vulnrichment marks CVE-2022-21894 as actively exploited
- AUG 9, 20226 public GitHub repositories claim a proof of concept for CVE-2022-21894
- Attack activity. OCT 22, 2026Exploitation of CVE-2022-21894 reported (CIRCL sighting)
- OCT 25, 2026CVE-2022-21894 discussed publicly (CIRCL sighting) (6 reports, latest NOV 9)
SOURCES
- [1] CIRCL Vulnerability-Lookup sightings: CVE-2022-21894 discussed publicly (CIRCL sighting), NOV 9
- [2] CIRCL Vulnerability-Lookup sightings: Exploitation of CVE-2022-21894 reported (CIRCL sighting), OCT 22
- [3] PoC-in-GitHub: 6 public GitHub repositories claim a proof of concept for CVE-2022-21894, AUG 9
- [4] CVE List V5 and CISA Vulnrichment: CISA Vulnrichment marks CVE-2022-21894 as actively exploited, JAN 11
- [5] CIRCL Vulnerability-Lookup sightings: 5 more reports