Science & TechnologyLOT 261120 · 3 min read
Windows 11 Lock Screen Zero-Day Defeats BitLocker With a Few Keystrokes
A fresh Windows 11 lock screen zero-day from researcher Nightmare Eclipse lets attackers bypass the login screen with Win+U, run code as the user, and sidestep BitLocker protection entirely.
Key takeaways
- Zero-day disclosed by Abdelhamid Naceri (Nightmare Eclipse), his roughly 12th Windows zero-day find
- Exploit needs only a keyboard: Forgot my PIN, then Win+U, then Caps Lock navigation
- Allows running USB payloads or creating admin accounts as the logged-in user
- BitLocker offers no protection because the session volume is already unlocked
- Independently reproduced by a sysadmin on Intune-enrolled devices

A zero-day in the Windows 11 lock screen lets an attacker with nothing but a keyboard run software as the logged-in user — a scenario BitLocker is specifically meant to defeat. Researcher Abdelhamid Naceri, better known as Nightmare Eclipse, disclosed the flaw, which may also affect Windows 10. He claims credit for roughly a dozen Windows zero-days, so the report deserves the benefit of the doubt until patch day settles the matter.
The attack requires physical access to the machine. That caveat sounds reassuring until you remember that physical access is exactly the threat model lock screens and full-disk encryption exist to address. A laptop left in a hotel room is the canonical case, and this bug appears to open it wide.
How does the keystroke sequence work?
The recipe is short. On the Windows 11 lock screen, the attacker clicks "Forgot my PIN," then presses Win+U to summon the Narrator accessibility window. The window renders behind the lock screen, which turns out to be, in practical terms, a veneer. By holding Caps Lock and using the arrow keys and Enter, the attacker navigates the hidden window by keyboard alone.
A brief walk through Narrator's menus lands the attacker in the full Settings app. From there, the paths branch:
- Open Bluetooth and Devices, set Autoplay to display a USB stick's contents, then plug in a stick carrying the payload of choice and run it.
- On a personal machine, where the legitimate user almost certainly holds administrator rights, simply create a new local account with admin privileges.
Either route executes code in the context of the signed-in user. If the disk is BitLocker-encrypted but the volume is unlocked at the lock screen, the encryption offers no additional barrier. The screen is locked; the data, evidently, is not.
How reliable is the exploit?
The bug is fresh enough that independent testing remains thin. Naceri's own assessment is blunt: "the vulnerability seems to be extremely consistent in every machine I tested it in." One system administrator on Reddit, posting as danrhodes1987, reports reproducing it on machines he manages, though only on his Intune-enrolled devices. His verdict: "you can launch anything you want in the context of the user logged onto the device."
The same administrator found a second, arguably worse capability. He could navigate, invisibly, whatever programs the user had left open before locking the screen. That makes the victim's running applications and their data effectively accessible in full, not merely the file system.
A caveat is warranted. One Reddit reproduction on Intune-managed hardware is not a fleet-wide audit, and Microsoft has yet to publish its own assessment. Consistency claims from the researcher and one sysadmin are encouraging, in the way a fire alarm is encouraging to an arsonist, but broader confirmation should follow.
What does this mean for the lock screen itself?
The structural lesson may outlast this particular bug. One veteran Windows sysadmin, consulted for this story, remarked that the lock screen implementation has always felt like a kludge bolted onto the session model, and predicted this will not be the last hack found against it. Accessibility features that spawn windows before authentication are a recurring soft spot, and Narrator is now on that list.
For enterprises, the immediate exposure is confined to machines an attacker can physically reach while a session stays signed in. Power users can mitigate the Autoplay path by disabling it outright. Until Microsoft ships a fix, the honest summary is that the lock screen now guards approximately as well as a curtain, and administrators should plan their patch deployment accordingly.
Tom's Hardware (Source)
More from Nathan Brooks
Show full bio
Senior reporter covering people, launches and day-to-day practice in Semiconductors, chip manufacturing, hardware, AI compute at Chip Dispatch.
1,147 articles