FastUnlock Windows 0-Day: Locked PCs Can Run Code

Introduction
A newly disclosed technique called FastUnlock allows someone standing in front of a locked Windows computer to start programs on that machine without ever signing in. The method is currently unpatched, was published publicly this week by a researcher who operates under the handles MSNightmare and Nightmare Eclipse, and has also been associated with endpoint-security firm ThreatLocker. The practical consequence is uncomfortable for anyone who treats a locked screen as a security boundary: it is not one.
There is an important limit to the story. According to the disclosure, whoever exploits FastUnlock receives only a limited account rather than administrator control of the machine. That makes it less severe than a full local privilege-escalation flaw, but it would be a mistake to dismiss it. A restricted session on a trusted corporate endpoint is still a foothold, and footholds are what attackers convert into real intrusions.
What FastUnlock actually does, and what it does not
The technique targets the gap between a machine being locked and a machine being logged in. Normally, the lock screen is meant to prevent anyone without credentials from interacting with the operating system beyond the sign-in prompt. FastUnlock lets a person with hands-on access break out of that constraint and launch programs on the device.
Two boundaries define the risk:
- Physical access is required. This is not a remote, wormable or network-exploitable issue. An attacker has to be at the keyboard.
- The resulting context is limited. The disclosure states that the session does not grant administrator rights, so the technique on its own does not hand over the machine.
What is not yet public matters just as much. There is no published CVE identifier, no vendor advisory, no confirmed list of affected Windows versions, and no confirmed remediation timeline. Readers should treat any specific version claims circulating on social media with caution until Microsoft or the researcher publishes details. The disclosure is fresh, and the technical write-up will likely be scrutinised and refined by other researchers in the coming days.
Why a limited session is still a serious problem
Security teams often rank local, physical-access issues below remote code execution because the attacker is assumed to already be inside the building. That assumption breaks down in several common environments: shared workstations in clinics and factory floors, hot-desking offices, retail and branch locations, laptops left in vehicles or hotel rooms, and any kiosk or lab machine that a visitor can reach.
More importantly, a limited account is not a dead end. An attacker who can run programs on a locked endpoint can potentially run tooling that does not require elevation, probe the local environment, reach network resources the logged-in user can access, or simply leave something running for later. The value of the technique is that it turns a few minutes of unsupervised physical proximity into execution on a managed device, bypassing the expectation that a locked screen means no code runs.
It also undermines a control many organisations rely on implicitly: the belief that lock-screen state is a trustworthy signal. Endpoint telemetry, asset inventories and access logs frequently assume that a locked device is inert. FastUnlock challenges that assumption directly.
What defenders should do now
Because no patch exists, mitigation has to come from controls around the endpoint rather than inside it. Practical steps include:
- Treat physical access as a security control. Enforce cable locks, locked rooms and cabinets for shared and public-facing machines, and tighten visitor handling in areas with unattended PCs.
- Shorten the exposure window. Aggressive lock-screen timeouts and automatic session termination reduce the time an unattended, locked machine is reachable.
- Harden the boot chain. Full-disk encryption with pre-boot authentication and a measured boot configuration makes offline tampering with a device considerably harder.
- Apply application control. Allowlisting limits what can execute on an endpoint regardless of which account context is used, which blunts the value of a limited session.
- Restrict local account rights. Review which accounts exist on endpoints, remove unnecessary local administrators, and audit who can log on locally.
- Hunt for anomalies. Ask your EDR whether it would alert on process creation occurring while a session is locked. If the answer is unclear, that is a detection gap worth closing.
- Watch for the patch. Monitor Microsoft advisories and the researcher's publication for affected version details and a fix, and be ready to test and deploy quickly.
Conclusion
FastUnlock is a reminder that lock screens are convenience features, not security boundaries, and that the physical layer is still part of the attack surface for Windows estates. The absence of a patch makes process discipline the only defence available today, and the limited account context makes it a supporting technique rather than a headline compromise. Organisations that pair hardened endpoints with automated detection and response, of the kind Grivyonx delivers through its AI automation, DevSecOps and cloud security work, are better placed to spot the unusual execution that follows a bypass like this one.
Grivyonx Expert Analysis
The most interesting thing about FastUnlock is not the technique itself but the assumption it punctures. Most Windows hardening guidance quietly treats the lock screen as a trust boundary, and many detection stacks do the same. A bypass that yields only a limited account will be filed by some teams as low severity and deprioritised, which is precisely the wrong instinct. Low-privilege execution on a managed endpoint is the first stage of most intrusions, and the attacker here did not need a phish, a credential or a remote service. Defenders should use this disclosure as a prompt to test two things: whether their endpoint telemetry would surface program execution from a locked session, and whether application control would stop it. If either answer is no, the gap exists independently of whether FastUnlock is ever patched.
Final thoughts
Expect the technical details to evolve as other researchers reproduce the method and as Microsoft responds. Until then, the sensible posture is to assume that a locked Windows machine with physical access is a machine someone can run code on, and to design your physical, encryption and application-control layers accordingly.
- #FastUnlock
- #Windows zero-day
- #physical access attacks
- #endpoint security
- #lock screen bypass
- #ThreatLocker
- #Windows hardening



