# FastUnlock: unpatched Windows 11 lock-screen bypass via Narrator needs physical access. What to do now

> A researcher has published FastUnlock, a Windows 11 26H2 zero-day that uses Narrator and the account-recovery screen to run code on a locked PC. There is no patch or CVE yet, so laptops that could be lost or stolen need a BitLocker pre-boot PIN and closer physical control.

Published Nov 21, 2026 by TechMeasured Staff · Security · Canonical: https://techmeasured.com/security/fastunlock-windows-11-lock-screen-bypass-narrator-bitlocker-claim-unpatched-what-to-do

A researcher who goes by Chaotic Eclipse (also Nightmare-Eclipse and MSNightmare) on November 19 published **FastUnlock**, an unpatched Windows 11 flaw that lets someone with a locked PC in their hands open File Explorer and run programs without signing in. Security Affairs and Borncity report that it works on **Windows 11 26H2 with the November 2026 updates installed**. Security firm ThreatLocker says it reproduced the lock-screen bypass the same day.

Why it matters: this is a lost-or-stolen-laptop problem. The attacker needs the physical machine, but the researcher claims the trick also gets past BitLocker on a PC that is already running, because the drive is unlocked at that point. Microsoft had issued no advisory, CVE or update as of Borncity's November 19 report, and Born's November 21 follow-up mentions no fix either.

## How it works

The three write-ups describe the same chain:

1. On the lock screen, choose the "I forgot my PIN" (or password) option to reach the Microsoft account recovery screen.
2. Start Narrator, Windows' screen reader (Borncity says with Windows+U), and use it to reach the Settings window.
3. Move through Bluetooth & devices to AutoPlay, which opens File Explorer.
4. Run code from a USB drive.

Code runs as **WsiAccount**, the account the lock screen itself uses. ThreatLocker says that account is not an administrator. Günter Born attributes the bug to a redesigned Narrator interface that is not blocked when it runs as the lock-screen user.

| | What the sources say |
|---|---|
| Access needed | Physical access to the PC |
| Account needed | At least one user account linked to a Microsoft (online) account |
| Tested version | Windows 11 26H2, November 2026 patches |
| Windows 10 | Not tested, per the researcher |
| Result | Code execution as WsiAccount (non-admin, per ThreatLocker) |
| Patch / CVE | None reported as of Nov 19–21 |
| Exploitation in the wild | None known, per Borncity |

The researcher says it took **about five minutes** from finding the bug to breaching a fully BitLocker-encrypted machine. That is a time-to-discovery boast, not a measure of how long an attack takes.

## What is confirmed and what is not

ThreatLocker's team reproduced the lock-screen access to WsiAccount using an external drive. It notes that the physical keyboard did not work while navigating with Narrator, so it used the on-screen keyboard. Its write-up does not claim to have verified the BitLocker angle. Borncity says the public demo shows File Explorer opening from the locked state, not code execution, and that independent confirmation of the full claim was still pending. A reader comment cited by Born says Reddit users think SYSTEM-level access may also be reachable. Born says that still needs testing, and we have seen no evidence for it.

## What to do

- **Turn on a BitLocker pre-boot PIN** for laptops and other PCs that leave the building. ThreatLocker and Born both say a PIN at startup protects a machine that is powered off or hibernated, because the drive stays locked until the PIN is entered. It does not help a PC that is running and sitting at the lock screen.
- **Shut down or hibernate instead of sleeping** when a device is travelling or left unattended, so the pre-boot PIN applies.
- **Consider blocking Narrator** until Microsoft ships a fix. The researcher suggests blocking it fully with AppLocker or a changed access-control list (DACL), according to Borncity. That will affect anyone who relies on the screen reader, so check with users first.
- **Treat third-party scripts with care.** Born links a reader-published PowerShell mitigation on GitHub. We have not reviewed it. Test anything like that before rolling it out.
- **Watch for Microsoft's response.** For a similar BitLocker bypass in May (YellowKey, CVE-2026-45585), Microsoft responded with a mitigation in May, Borncity notes, so an interim workaround may come before a patch.

Who should care most: IT teams managing laptop fleets, especially devices signed in with Microsoft accounts. Desktops in locked offices are at much lower risk, because the attack needs hands on the machine.


## Sources

1. [Security Affairs — Chaotic Eclipse Releases FastUnlock, a New Windows Zero-Day Vulnerability](https://securityaffairs.com/203537/hacking/chaotic-eclipse-releases-fastunlock-a-new-windows-zero-day-vulnerability.html)
2. [ThreatLocker — Proof of Concept for FastUnlock, Windows lock screen bypass from Nightmare Eclipse](https://www.threatlocker.com/blog/proof-of-concept-for-fastunlock-windows-lock-screen-bypass-from-nightmare-eclipse)
3. [Borncity — FastUnlock: Windows-11-Lücke soll BitLocker in fünf Minuten umgehen](https://borncity.com/news/fastunlock-windows-11-luecke-soll-bitlocker-in-fuenf-minuten-umgehen/)
4. [Born's IT- und Windows-Blog — Windows 11 26H2: MSNightmare veröffentlicht FastUnlock 0-Day](https://borncity.com/blog/2026/11/21/windows-11-26h2-msnightmare-veroeffentlicht-fastunlock-0-day/)
