--- title: "FastUnlock Windows Lock-Screen Zero-Day: Who Is at Risk" url: https://playciso.com/blog/windows-fastunlock-lock-screen-zero-day updated: 2026-11-20 section: Blog publisher: PlayCISO --- # FastUnlock Windows Lock-Screen Zero-Day: Who Is at Risk > FastUnlock lets someone holding a locked Windows PC run a program as a limited account. No patch or CVE yet. Who is at risk, BitLocker PINs, what to do. Source: https://playciso.com/blog/windows-fastunlock-lock-screen-zero-day · Published: 2026-11-20 · Publisher: PlayCISO (https://playciso.com) Primary source: https://github.com/MSNightmare/FastUnlock --- **FastUnlock** is an **unpatched Windows zero-day technique** that can let someone with **physical access** run a program on a **locked computer without signing in**. It was published on GitHub on **19 November 2026** by the researcher using the handles MSNightmare and Nightmare Eclipse. **ThreatLocker** tested it independently the same day and could launch a program, but only as **WSIAccount, a limited account that is not an administrator**. There is **no fix, no CVE and no evidence of real-world exploitation**. **Who this is for:** security and IT leaders responsible for Windows laptops that travel, shared desks, kiosks and front-counter PCs, and anyone who relies on BitLocker for lost-device risk. *Based on the researcher's GitHub post, ThreatLocker's test write-up, Microsoft's BitLocker and TPM documentation, and reporting by The Hacker News and Security Affairs. We describe the technique at a high level only and give no steps. PlayCISO is not affiliated with any of them. Facts as reported on 20 November 2026.* Confirmed vs not yet known **Independently tested (ThreatLocker):** from the lock screen, a program could be launched as WSIAccount, which ThreatLocker says is "not an administrator account". It needed physical access and a Microsoft account available through the account recovery flow. **Researcher says:** tested on Windows 11 26H2 with the November 2026 updates; at least one account on the machine must be linked to an online account; other versions, including Windows 10, not tested. **Not established:** a list of affected Windows versions; whether domain-joined or Entra-joined work devices behave differently; exactly what WSIAccount can read on a typical machine; any Microsoft statement, CVE or fix. **Not reported:** any use in real attacks. ## What FastUnlock is, at a high level The technique abuses **Narrator**, the screen reader built into Windows, from the lock screen's **Microsoft account recovery** option. The researcher says a redesigned Narrator interface can run in the lock screen's own account context, which Microsoft did not prevent. From there, per ThreatLocker, a person at the keyboard can reach a point where they start a program that runs as WSIAccount. ThreatLocker's proof of concept brought the program in on an external drive and notes that other ways exist. We are not publishing the steps; nothing below needs them. **The conditions**, per the researcher, ThreatLocker and The Hacker News: - Physical access to the computer. This is not a remote attack. - A Microsoft account reachable through the lock screen's recovery options; the researcher phrases it as at least one account on the machine linked to an online account. - The machine must be started and at the lock screen, with its drive already unlocked (see the BitLocker section). The Hacker News notes it does not work on every machine. By the researcher's stated condition, a computer with only local accounts would not qualify, but nobody has published a test of that, and no source covers domain-joined or Entra-joined corporate devices. ## What an attacker gets: a limited account, not admin ThreatLocker's test reached **WSIAccount**, an account Windows uses at the lock screen, and it says this is **not an administrator account**. ThreatLocker's overview describes the reported technique as letting a person run code and access files without signing in to a user account, but neither ThreatLocker nor the researcher lists which files or settings WSIAccount can actually read. Nothing published shows it giving administrator rights, the signed-in user's session or their credentials. That still matters. A program running on a machine you do not control, with access to anything a non-administrator account can read on that disk, is a foothold. Whether it becomes more depends on what else is unpatched on the machine. Assume that someone who can chain it with a local privilege escalation flaw will try. ## The BitLocker point: it does not break encryption Headlines say FastUnlock bypasses BitLocker. The precise version: **FastUnlock does not break BitLocker or recover its key**. It works **after the computer has already unlocked its drive automatically during startup**. In BitLocker's default **TPM-only** mode, the TPM releases the key at boot with no input from the user. Microsoft's [BitLocker countermeasures page](https://learn.microsoft.com/en-us/windows/security/operating-system-security/data-protection/bitlocker/countermeasures) says TPM-only "doesn't require any interaction with the user to unlock and provide access to the drive", and The Hacker News quotes [Microsoft's TPM documentation](https://learn.microsoft.com/en-us/windows/security/hardware-security/tpm/how-windows-uses-the-tpm) describing unlocking "without having to enter a PIN". So by the time the lock screen appears, the files are readable by the running Windows. The lock screen is then the only barrier, and FastUnlock goes around it. **Why that matters for laptops:** a laptop is the device most likely to be left at a lock screen in a hotel, a train or a conference room, and most likely to be stolen while on or asleep. Microsoft's own guidance says a device resumed from **sleep** does not ask for the PIN again, while one resumed from **hibernation** does. **What a startup PIN does and does not do.** A BitLocker startup PIN (TPM plus PIN) stops the drive unlocking until someone types the PIN, so a **powered-off or hibernated** laptop cannot be brought to the lock screen by a thief. ThreatLocker says a preboot PIN helps if the device was just powered on. It **does not protect a device already at the lock screen**: the PIN was entered at boot and the drive is open. ## Timeline | Date | What | Source | | --- | --- | --- | | 19 Nov 2026 | The researcher (MSNightmare / Nightmare Eclipse) publishes FastUnlock on GitHub: a short post and video, tested on Windows 11 26H2 with the November 2026 updates | GitHub, The Hacker News | | 19 Nov 2026 | ThreatLocker tests the technique and reaches WSIAccount, "not an administrator account" | ThreatLocker | | 19 Nov 2026 | Security Affairs reports the release, notes no full code execution demo from the researcher and no Microsoft response | Security Affairs | | 20 Nov 2026 | The Hacker News: no fix from Microsoft, no official list of affected versions, no evidence of real-world use | The Hacker News | ## What security leaders should do this week - Add a BitLocker startup PIN to laptops that travel or hold sensitive data. Microsoft's countermeasures guidance recommends TPM with a PIN against an attacker with time and physical access. Start with executives, finance, engineering and anyone who flies; expect help-desk calls about forgotten PINs and plan for them. - Shut down or hibernate, do not just lock or sleep. Microsoft recommends shutting down or hibernating a device "before it leaves the control of an authorized user", and notes that resuming from sleep does not ask for the PIN. Tell staff plainly: a locked screen is not enough when the laptop leaves your hands. - Never leave a device at the lock screen unattended in risky places. Hotel rooms, airport lounges, conference halls, shared offices. Until Microsoft ships a fix, treat an unattended locked Windows PC as a PC someone can run a program on. - Lock down shared and front-counter PCs. The Hacker News singles out shared desks and front-counter computers. Physically secure them, keep them in sight of staff and check which of them have a Microsoft account linked. - Know which devices meet the condition. Find Windows devices where an account is linked to a Microsoft account. That is your likely exposed set, not every Windows machine. Record the gap and its owner in your [risk register](/tools/risk-register) until a fix ships. - Do not improvise accessibility lockdowns. No source and no Microsoft documentation we read names a setting that blocks this technique. Turning off Narrator for everyone would hurt staff who rely on it. Wait for Microsoft's guidance. - Treat removable-storage control as a partial measure. ThreatLocker's proof of concept used an external drive to bring the program in, but it notes other methods exist, so blocking USB storage narrows one route without fixing the flaw. - Watch for the fix and rank it when it lands. Track the [Microsoft Security Update Guide](https://msrc.microsoft.com/update-guide). When a CVE appears, put it through the [vulnerability prioritizer](/tools/vulnerability-prioritizer): a physical-access flaw with a public write-up can still be urgent for a mobile workforce. - Rehearse the lost-device call. Who decides whether a stolen laptop's data counts as exposed, and on what evidence? Build the scenario with the [tabletop runbook generator](/tools/tabletop-runbook-generator), and practise the insider side of physical access in the [insider data theft lab](/tools/insider-data-theft-lab). No source has published detection guidance for FastUnlock yet. Background on layered endpoint controls: [operating system security fundamentals](/blog/operating-system-security-fundamentals-free-guide). Another unpatched zero-day with no CVE this week: [Danfoss AK-SM800A](/blog/danfoss-ak-sm800a-zero-days-midnight-blue). ## Where sources differ - Code execution. Security Affairs says the researcher's demo does not show full code execution; ThreatLocker says its test could launch a program as WSIAccount. - "BitLocker bypass". The researcher says it gets past BitLocker on a fully encrypted machine. The Hacker News says it does not break BitLocker or recover the key; it works on a machine that has already unlocked its drive. Both are describing the same thing from different ends: the encryption holds, the lock screen does not. ## Microsoft's response None found. As of 20 November 2026, no source we read reports a Microsoft statement, security advisory, CVE or fix for FastUnlock. The researcher's post blames Microsoft for the flaw. Security Affairs notes that some of the same researcher's earlier Windows releases were later exploited in the wild, which is a reason to apply the controls above now rather than wait. ## FAQ ### What is FastUnlock? FastUnlock is the name a researcher using the handles MSNightmare and Nightmare Eclipse gave to an unpatched Windows lock-screen bypass published on GitHub on 19 November 2026. Per the researcher and ThreatLocker, someone with physical access to a locked Windows computer can use the Narrator screen reader during the Microsoft account recovery flow to run a program without signing in. The program runs as a limited account, not as an administrator. ### Has anyone confirmed that FastUnlock works? Yes, one independent party. ThreatLocker says its Threat Intelligence team tested the technique on 19 November 2026 and reached the WSIAccount user, which it says is not an administrator account. Security Affairs noted on the same day that the researcher's own public demo stops short of showing full code execution. Microsoft has not commented in any source we read. ### What does an attacker get from FastUnlock? A program running under WSIAccount, a limited account Windows uses at the lock screen. ThreatLocker says it is "not an administrator account". No source has listed exactly which files or settings that account can read on a typical machine, and nothing published shows it giving administrator control or the signed-in user's session. ### Does FastUnlock break BitLocker? No. It does not break BitLocker encryption or recover the key. It works after the computer has already unlocked its drive during a normal startup, which BitLocker does automatically with the TPM in its default TPM-only mode. The researcher describes this as getting past BitLocker; the more precise reading, per The Hacker News, is that BitLocker had already unlocked the drive before the lock screen appeared. ### Does a BitLocker startup PIN stop FastUnlock? It stops it on a machine that is powered off or hibernated, because nobody reaches the lock screen without the PIN. ThreatLocker says a preboot PIN helps if the device was just powered on. It does not protect a device that is already started and sitting at the lock screen, or one resumed from sleep, because the drive is already unlocked. ### Which Windows versions are affected by FastUnlock? No official list exists. The researcher says they tested Windows 11 26H2 with the November 2026 updates installed, have not tested other versions and are not sure about Windows 10. Treat any Windows device that meets the conditions as possibly affected until Microsoft says otherwise. ### Are computers with only local accounts affected? The researcher says at least one account on the machine must be linked to an online Microsoft account, and The Hacker News describes the condition as a Microsoft account reachable through the lock screen's recovery options. By that stated condition, a machine with only local accounts would not qualify, but nobody has published a test of that. No source addresses domain-joined or Entra-joined work devices. ### Is FastUnlock being exploited and is there a CVE or patch? No source reports exploitation in real attacks. As of 20 November 2026 there is no CVE, no Microsoft security advisory and no fix. Security Affairs notes that some of the same researcher's earlier releases were later exploited in the wild, so watch for an update. ### What should organisations do about FastUnlock this week? Add a BitLocker startup PIN to laptops that travel or hold sensitive data, and have staff shut down or hibernate them rather than sleep or lock them when they leave their hands. Do not leave devices at the lock screen unattended in public or shared spaces, lock away or closely manage shared and front-counter PCs, and track Microsoft's update guide for a fix. ## Sources - [MSNightmare (Nightmare Eclipse): FastUnlock on GitHub](https://github.com/MSNightmare/FastUnlock) (19 Nov 2026): the original disclosure; requirements and tested version - [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) (Kenneth Walker, 19 Nov 2026): the independent test, WSIAccount, preboot PIN - [Microsoft Learn: BitLocker countermeasures](https://learn.microsoft.com/en-us/windows/security/operating-system-security/data-protection/bitlocker/countermeasures): TPM-only vs TPM plus PIN, sleep vs hibernate, shut down before the device leaves your control - [Microsoft Learn: How Windows uses the TPM](https://learn.microsoft.com/en-us/windows/security/hardware-security/tpm/how-windows-uses-the-tpm) - [The Hacker News: New unpatched Windows 0-day FastUnlock lets someone holding a locked PC run programs on it](https://thehackernews.com/2026/11/new-unpatched-windows-0-day-fastunlock.html) (20 Nov 2026) - [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) (19 Nov 2026) *As of 20 November 2026. We will add the CVE, Microsoft's advisory and the affected versions when Microsoft publishes them. This article is educational guidance for security leaders, not legal advice.*