FastUnlock: New Unpatched Windows 0-Day Lets Anyone at a Locked PC Launch Programs

A researcher has disclosed an unpatched technique that allows someone with physical access to a locked Windows machine to launch programs without ever signing in. Dubbed FastUnlock, the method was published by a researcher operating under the handles MSNightmare and Nightmare Eclipse, with analysis following from endpoint-security firm ThreatLocker.

The headline risk is narrower than it first sounds—but still significant. According to the disclosure, anyone who exploits FastUnlock only gains a limited account context, not administrative control of the device. Even so, the ability to execute code on a machine that appears locked undermines a core assumption many organizations rely on: that a locked screen means no one can interact with the endpoint.

What FastUnlock Actually Does

The technique targets the Windows lock screen—the state a workstation enters when a user walks away or the session times out. Normally, the lock screen is meant to be a hard boundary: input is accepted only to authenticate, and no user-level code should run until credentials are verified.

FastUnlock appears to break that boundary, letting a person at the keyboard start programs without signing in. The resulting session is constrained to a limited account, which caps the blast radius. An attacker cannot simply take over the machine as an administrator, and the technique does not by itself grant access to another user's protected data or elevated system functions.

That limitation matters for prioritization, but it should not be read as reassurance. Limited execution is frequently the first step in a longer chain. An attacker with even a low-privilege foothold on a physically accessible device can attempt privilege escalation, drop tooling, probe the local network, or stage activity that survives a reboot—depending on what the environment allows.

Why Physical Access Still Matters

Physical access attacks are often dismissed as out of scope in threat models that assume a locked door and a trusted workforce. In practice, laptops travel. They sit in hotel rooms, conference rooms, shared offices, and vehicles. Kiosks and lab machines are frequently left unattended in semi-public spaces. A technique that requires only a few minutes at a keyboard is therefore a realistic concern for organizations with mobile workforces, contractors, or any population of devices that leave controlled facilities.

Because the method is unpatched at the time of disclosure, there is no vendor fix to deploy. Mitigation has to come from controls that do not depend on Microsoft shipping an update.

Practical Mitigations

  • Treat locked devices as exposed. Reinforce policy that unattended machines should be powered down or hibernated rather than merely locked, particularly when traveling or working in shared spaces.
  • Harden the local attack surface. Restrict which applications can run through application control and allowlisting, so that even limited-context execution is constrained to approved binaries.
  • Reduce standing local privileges. Minimize the number of accounts with local administrator rights and audit local group membership, since escalation from a limited account is the most likely next move.
  • Monitor for anomalous process activity. Endpoint detection should flag unexpected process creation tied to lock-screen or logon-related components, and correlate it with the absence of a corresponding authentication event.
  • Enable full-disk encryption and strong pre-boot authentication. These do not stop FastUnlock directly, but they limit what an attacker can extract from a device they can physically touch.
  • Watch for a vendor response. Track Microsoft's guidance and any advisory updates; unpatched disclosures frequently evolve as the vendor investigates.

The Bigger Picture

FastUnlock is a reminder that the lock screen is a user-interface convention, not a security boundary in the way administrators often imagine. Windows has a long history of lock-screen and logon-screen weaknesses, and each new variant tends to be treated as an edge case until it appears in a real intrusion.

The limited-account constraint is genuinely good news for defenders—this is not a full authentication bypass. But the disclosure also arrives without a patch, which means the window of exposure is open-ended. Organizations should use the time to verify that application control, least privilege, and endpoint monitoring are actually functioning on the devices most likely to be physically reachable, rather than assuming a locked screen is doing work it was never designed to do.

For defenders, the practical question is not whether FastUnlock grants administrator rights—it does not—but whether a limited-context execution primitive on an unattended laptop would be enough to start something worse in their environment. In many networks, the honest answer is yes.

Source: The Hacker News – New Unpatched Windows 0-Day FastUnlock