FastUnlock: An Unpatched Windows 11 Lock-Screen Bypass Runs Through Narrator and Needs the Laptop in Hand. A BitLocker Startup PIN Plus Hibernate, Not Sleep, Is the Defense Today
If your laptops use BitLocker with automatic TPM unlock and go to sleep with the lid closed, a published technique called FastUnlock lets someone holding the locked machine reach a program-launching path without signing in. There is no Microsoft fix and no CVE as of Friday, November 20, 2026. What protects you today: a BitLocker startup PIN, and machines that are shut down or hibernated (not asleep) whenever they leave your hands.
What was published
A GitHub account named MSNightmare created the repository FastUnlock on Thursday, November 19, 2026 at 12:37 UTC, described as "Windows Narrator LockScreen Bypass 0day Vulnerability." ThreatLocker and The Hacker News attribute it to the researcher known as Nightmare Eclipse, the same handle behind the YellowKey BitLocker bypass we covered in June. The repository holds a README, a license and a link to a demo video. It contains no exploit code: the "proof of concept" is a sequence of key presses.
The researcher's description: "The vulnerability exist in the way how narrator handles UI in a locked account context, succesful exploitation results in bypassing bitlocker and executing code in the context of the lockscreen account 'WsiAccount'."
The path, as the README lays it out:
On the lock screen, click "I forgot my PIN" (or password).
When the Microsoft account reset window appears, press Win+U and turn on Narrator.
Narrator focuses on a hidden window it owns. Holding Caps Lock with the arrow keys, navigate to "Math reading settings" and activate it with Caps Lock + Enter. That opens the Settings app.
From Settings, the researcher's preferred route is Bluetooth and devices, then AutoPlay, then Removable drive, then "Open folder to view files (File Explorer)."
Plug in a USB drive, browse it in Explorer with Narrator, and run a program from it as WsiAccount.
The researcher's explanation of the root cause: in giving Narrator a new interface, "Microsoft forgot to make sure that the new UI does not run in the case it was running in the context of a lockscreen user," while the older check that stops the window when running as SYSTEM is still there.
What is confirmed and what is only claimed
Physical access is required. The researcher says so plainly: "Obviously this needs physical access and at least one account in the machine to be linked to an online account." This is not a remote bug.
One precondition: a Microsoft account on the machine. The entry point is the Microsoft account recovery flow. A machine where no account is linked to an online account is outside the conditions the researcher describes. Whether work accounts (Entra ID) count as "online accounts" here is not stated by either source we read. Treat that as unknown.
Tested version: one. The researcher tested Windows 11 26H2 with the November patch installed and wrote: "I have not checked other windows versions so I am not really sure if this might work on windows 10." No official list of affected versions exists.
The full code-execution step was not shown in the researcher's video. In the README's words: "I didn't show the full code execution demo because I don't really have a USB stick but I already did this enough times to know what happens next." The video stops at Explorer.
ThreatLocker tested it independently. Kenneth Walker's write-up (November 19) says the bypass reached the WSIAccount user, which it describes as "not an administrator account," and that they "used an external drive for this PoC." They could not type on the physical keyboard while driving Narrator and used the on-screen keyboard instead. ThreatLocker does not name the Windows build it tested.
It does not break BitLocker's encryption. FastUnlock runs on a machine that has already unlocked its drive at boot. On a TPM-only setup, that happens automatically when the machine starts, so the drive is readable before anyone touches the lock screen. "Bypassing bitlocker" in the README means getting past a locked screen on an unlocked drive, not recovering a key.
What WsiAccount can read or do on the machine is not documented. It is a limited, non-admin lock-screen account per ThreatLocker. Neither source shows it reading another user's files or escalating. A non-admin foothold on an unlocked machine is still a foothold, and the researcher has a track record of local privilege-escalation bugs, so plan on it being chained.
No exploitation in the wild has been reported in any source we read. No Microsoft statement, advisory or CVE was found by our searches on November 20.
There is nothing for us to watch on the network here. This is a hands-on-keyboard bug with no network indicators, so there is no edge check to run and nothing to add to the feed.
What to do today
Add a BitLocker startup PIN on laptops and any machine that leaves a locked room. Group Policy: Computer Configuration, Administrative Templates, Windows Components, BitLocker Drive Encryption, Operating System Drives, "Require additional authentication at startup," with "Configure TPM startup PIN" set to require or allow a PIN. Intune has the same setting in its BitLocker profile. ThreatLocker's verdict on this: a preboot PIN "will help mitigate this if the device was just turned on." It does nothing for a machine that is already running.
Make "leaving my hands" mean hibernate or shut down, not sleep. A sleeping laptop has its drive unlocked and sits at the lock screen, which is exactly where FastUnlock starts. Set the lid-close and power-button actions to Hibernate (Control Panel, Power Options, "Choose what closing the lid does"), and set a short hibernate timeout. Hibernate with a startup PIN puts the attacker back in front of the PIN prompt.
Treat a locked screen as a speed bump for unattended desks, kiosks and front-counter machines until Microsoft ships a fix. Physical control of the device is the control.
Partial and untested by us: close the researcher's preferred route. Turning off AutoPlay (Group Policy: Windows Components, AutoPlay Policies, "Turn off AutoPlay" for All drives) and blocking removable storage (System, Removable Storage Access, "All Removable Storage classes: Deny all access") target the USB step he uses. Do not rely on them: he says the Settings window "allows multiple ways to get code execution," and we have not tested whether either policy holds against this path.
Watch for Microsoft's fix and apply it when it ships. The researcher says: "hold tight any windows machines until Microsoft patches this."
Am I affected? Three checks per machine
Is any account on this machine a Microsoft account? Settings, Accounts, Your info: it says "Microsoft account" or "Local account." Then check Settings, Accounts, Other users. If none is linked to an online account, the researcher's stated precondition is not met.
Does BitLocker ask for a PIN at startup? In an admin prompt, run manage-bde -protectors -get C: and look for a protector named "TPM And PIN." If you only see "TPM," the drive unlocks itself at boot. (PowerShell alternative: Get-BitLockerVolume -MountPoint C: and read KeyProtector.)
Which Windows version is it? Run winver. Windows 11 26H2 with the November 2026 update is the one version tested by the researcher. Others are unknown, not safe.
If the answers are "yes, a Microsoft account," "TPM only" and "the laptop sleeps when the lid closes," that machine fits the conditions both sources describe.
How we know
We read the researcher's README in the MSNightmare/FastUnlock repository through the GitHub API (repository created 2026-11-19 12:37 UTC, last push 13:54 UTC), ThreatLocker's write-up of its own test, and The Hacker News report. All three trace to one disclosure; ThreatLocker's test is the only independent confirmation, and it is partial on the details (no build number, no explicit statement that a binary ran). We have not reproduced the technique. We found no Microsoft statement.
Sources
Researcher disclosure: https://github.com/MSNightmare/FastUnlock
ThreatLocker, proof-of-concept write-up by Kenneth Walker (November 19, 2026): https://www.threatlocker.com/blog/proof-of-concept-for-fastunlock-windows-lock-screen-bypass-from-nightmare-eclipse
The Hacker News, "New Unpatched Windows 0-Day FastUnlock Lets Someone Holding a Locked PC Run Programs on It" (November 20, 2026): https://thehackernews.com/2026/11/new-unpatched-windows-0-day-fastunlock.html
Microsoft, BitLocker countermeasures (startup PIN, hibernate): https://learn.microsoft.com/en-us/windows/security/operating-system-security/data-protection/bitlocker/countermeasures
Our YellowKey coverage, the same researcher's earlier BitLocker bypass: https://www.dugganusa.com/post/the-researcher-microsoft-tried-to-ban-also-handed-you-a-bitlocker-bypass-yellowkey-cve-2026-45585
Read next
The startup PIN is the fix here, and two days ago we wrote about how strong that PIN needs to be: A Stolen Laptop's Windows Hello or BitLocker PIN Can Be Brute-Forced by Rolling Back Its Firmware TPM Counter. The Fix Is Two More Digits.
Every indicator in this post is in the feed. Free.
1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.



Comments