A new Windows zero-day attack is reportedly getting past BitLocker using only the screen reader and a USB stick

Make compromises: BitLocker can be defeated in minutes on a fully patched Windows 11 computer, and the weapon is the OS’s own screen reader. A zero-day exploit released this week by a security researcher abuses Windows Narrator to execute code through the lock screen before a user logs in. There is no fix until Microsoft’s next Patch Tuesday, so encrypted machines will be exposed in the meantime.

The exploit, called FastUnlock, is entirely embedded in the software that ships with Windows. There is no malware download, no credential theft, and no memory corruption error required. It’s a logical error, and according to former Microsoft researcher Abdelhamid Naceri, it worked on every computer he tried.

The root of the issue lies between Narrator’s redesigned UI and the lock screen’s limited account context. Microsoft gave the screen reader a new look, but didn’t limit the updated interface to logged-in sessions.

Narrator can therefore be accessed while a computer is locked, where it runs under WsiAccount, the account under which the lock screen runs. This context should be isolated from the running system. Instead, it gives an attacker a code execution path that operates outside the protections that BitLocker and the login process are designed to enforce.

Triggering the chain requires only physical access and little else. On the lock screen, the attacker selects “I forgot my PIN” (or password) and waits for the Microsoft account window asking how to reset the account. Pressing Win+U and opening Narrator takes the screen reader to a background window that it owns, one that is never rendered on the screen and whose focus is already on a Next button.

The attacker never has to see it. Holding down Caps Lock and using the arrow keys will take you through the invisible window to a link labeled “Math Reading Settings.” Pressing Caps + Enter opens the Narrator settings, and from there a USB stick connected to the device is enough to access File Explorer and the user’s files.

Naceri said it took five minutes to find the problem and hack a fully encrypted, BitLocker-enabled computer running Windows 11 26H2 with the November 2026 patch installed. He blamed the mistake on what he called “total negligence” on Microsoft’s part.

However, the explosion radius is smaller than the technology suggests. Since there is no remote component, the attacker must be physically at the keyboard and know the correct key combination. The computer must also have at least one account linked to an online Microsoft account, as the reset flow that anchors the attack depends on it.

Devices running only local accounts are not affected. The attack also launches from a lock screen, meaning it targets drives that BitLocker has already unlocked at boot, as is the case with the standard TPM-only setup. A startup PIN would likely stop an attacker before the lock screen even loads, although this hasn’t been tested. For everyone else, Naceri’s advice was blunt: “Hold on” until Microsoft releases a patch.

The revelation fits into a pattern that Naceri repeatedly causes headaches for his former employer. He is a security researcher based in Germany and says Microsoft fired him in 2024, months before he could secure permanent EU residency, over a security incident that he denies. He sued for unfair dismissal and emphasized that the dispute was never about bug bounties.

The public feud began in April when he released BlueHammer, a Microsoft Defender exploit, without notice, claiming that the company’s Security Response Center had ignored his reports and closed his account. Microsoft says it did not receive any details beforehand. Since then, he has released more than a dozen Windows zero days under the names MSNightmare, Chaotic Eclipse, Infinite Nightmare, and Nightmare-Eclipse, including YellowKey, an earlier BitLocker bypass. Microsoft took legal action before backing down, and at least three of its Defender exploits have been used in real attacks. This strategy comes at a cost to users: Once a technique is available on GitHub, any attacker can hijack it in the weeks between disclosure and Patch Tuesday.

The unpleasant detail for Microsoft is how little sophistication the attack requires. A redesigned UI component that should never have run in a locked account context is the entire vulnerability, and a keyboard and USB stick complete the rest. BitLocker remains as the encryption layer. What failed is the assumption that nothing on the lock screen can cross over into the running system.

Until the next patch cycle, the practical defense is the oldest in physical security: control over who can touch the machine.

Avatar photo
Written by

Mira Edora

Mira Edora is a writer and contributor at CKSOR, creating clear and engaging articles on current topics, technology, science, lifestyle, and stories of interest to readers. She enjoys researching new developments and presenting useful information in a simple, accessible way. Through her writing, Mira aims to keep readers informed with timely, informative, and easy-to-understand content.

Leave a Comment