Skip to main content
Emerging ThreatsMalware & Ransomware

Unpatched Windows Zero-Day Flaw Enables Program Execution on Locked PCs

Hand reaches for a locked Windows PC on an office desk.

A locked Windows machine can be made to run programs by someone who simply holds it: that is the immediate risk described by a newly disclosed, unpatched zero‑day technique called FastUnlock.

What FastUnlock does and how it was disclosed

The technique was posted by a researcher who uses the handles MSNightmare and Nightmare Eclipse and accompanied the disclosure with a short GitHub post and a video. The published post contained little written detail; the clearest public account comes from an independent test conducted the same day by the endpoint‑security firm ThreatLocker.

FastUnlock lets an attacker with physical access to a Windows PC start programs without signing into the device. The person who executes the technique receives only a limited account on the machine, not administrator control — ThreatLocker said the account it reached was identified as WSIAccount and is "not an administrator account." There is no fix from Microsoft yet, and ThreatLocker reported no evidence that the method has been used in the wild.

How ThreatLocker validated FastUnlock

ThreatLocker tested the disclosure on the same day it appeared and published its findings as the most detailed public test available. In that test the firm used Windows' built‑in screen reader, Narrator, to navigate the lock screen and the lock‑screen recovery options. The sequence allowed the tester to start a program from the lock screen inside the limited WSIAccount rather than completing a normal sign‑in.

The researcher’s GitHub post contained a video but minimal explanation; ThreatLocker’s hands‑on test provides the operational detail that establishes the technique’s feasibility under certain conditions.

Why BitLocker plus TPM does not automatically block FastUnlock

Many Windows machines use BitLocker disk encryption. However, in a common configuration the device’s Trusted Platform Module (TPM) unlocks the drive automatically when the computer starts, so by the time the lock screen appears the disk is already readable. Microsoft’s own TPM documentation describes this mode as one in which the drive unlocks "without having to enter a PIN."

FastUnlock does not break BitLocker encryption or recover encryption keys. Rather, it runs at the point after the drive has already been unlocked by the machine itself — a less severe technical outcome than cracking an encrypted disk, but still consequential for any device that someone else can hold and operate on the lock screen.

Practical mitigations users and administrators can apply now

  • Reduce physical exposure: Keep laptops, shared desks and front‑counter systems under controlled supervision; do not assume a locked screen alone is sufficient if someone else can handle the device.
  • Require a BitLocker startup PIN: On sensitive machines, configure BitLocker so the TPM does not unlock the drive automatically; adding a startup PIN prevents the machine from reaching the unlocked lock screen state an attacker needs.
  • Shut down or hibernate when devices leave control: A startup PIN protects only devices that have not yet started; once a device is on and sitting at the lock screen the FastUnlock sequence can run on machines that meet the other conditions.
  • Follow Microsoft guidance: Microsoft’s countermeasures guidance recommends using a startup PIN and shutting down or hibernating machines when faced with determined, hands‑on attackers; until an official patch or advisory appears, watch for one and apply it when released.

What this means for technologists, enterprises, and end users

Technologists and security teams will need to treat physical access as the threat vector of concern: configure BitLocker to require a startup PIN on highly sensitive endpoints, review shared‑device workflows, and update lock‑screen recovery settings where those options expose a reachable Microsoft account.

Enterprises and procurement leaders who supply laptops to staff or run public‑facing kiosks should reassess device lifecycle practices: ensure devices that could "go missing" are locked away or centrally managed and consider shutdown/hibernate policies for devices leaving custodial control.

End users should avoid relying solely on the visual lock screen. If a device might be handled by strangers — in a taxi, on a repair bench, or in a busy reception area — power it down or enable BitLocker startup PIN protection to reduce the risk that someone holding the machine can run programs from the lock screen.

FastUnlock is notable not because it cracks disk encryption but because it exploits the combination of physical access, reachable Microsoft account recovery options on the lock screen, and built‑in assistive features to achieve code execution in a limited account. The immediate practical question the facts leave open is when Microsoft will publish an advisory or a patch that clarifies which Windows versions are affected and how the company will remediate the lock‑screen recovery path used by FastUnlock.

Original reporting: https://thehackernews.com/2026/11/new-unpatched-windows-0-day-fastunlock.html