As reported by The Hacker News, a newly disclosed unpatched Windows zero-day technique dubbed FastUnlock allows an attacker with physical access to a locked Windows machine to execute programs without authenticating. The method, published by a researcher using the handles MSNightmare and Nightmare Eclipse, was independently validated by ThreatLocker on the same day. No CVE has been assigned, no patch exists, and no active exploitation has been observed.

Security Impact: As reported by The Hacker News, a newly disclosed unpatched Windows zero-day technique dubbed FastUnlock allows an attacker with physical access to a locked Windows machine to execute programs without authenticating.

This is not a remote attack. It requires physical access to the target device and a Microsoft account reachable through the lock screen's recovery options. The technique leverages Windows Narrator — the built-in screen reader — to navigate the locked interface and ultimately execute code in a limited context identified by ThreatLocker as WSIAccount, which is not an administrator account. The scope is constrained, but the implications for shared devices, kiosks, and unattended laptops are significant.

Why This Matters More Than It Looks

At first glance, a local privilege escalation to a non-admin account seems low-impact. The real concern is what an attacker can do from that foothold. A limited account on a live, unlocked-disk system can read files, exfiltrate data to a USB device or network location, plant persistence mechanisms for a later session, or reconnaissance the environment for follow-on attacks. If the disk is already BitLocker-unlocked — which is the default TPM-only configuration on most commercial Windows deployments — the attacker operates against a fully readable filesystem.

The most dangerous misunderstanding defenders may hold is that BitLocker with TPM-only protection shields them here. It does not. As Microsoft's own documentation describes, TPM-only mode unlocks the drive automatically at boot without requiring a PIN. By the time the lock screen appears, the filesystem is already decrypted and mounted. FastUnlock operates at that stage. The technique does not break BitLocker or recover keys — it simply runs code on a machine that has already decrypted itself.

Who Is Most at Risk

FactorRisk Level
Physical access requiredAttacker must have hands on the device
Microsoft account on lock screenDevices signed in with MS accounts with recovery options exposed
BitLocker TPM-only (no PIN)HIGH — disk is auto-unlocked at boot
Shared/kiosk/front-counter PCsHIGH — accessible to strangers
Laptops in transit or unattendedMEDIUM-HIGH — theft grants attacker unlimited time
BitLocker with pre-boot PINLOW — disk remains encrypted if attacker reboots

The Narrator Attack Surface Pattern

FastUnlock is the latest in a recurring pattern of Windows accessibility tools being weaponized from the lock screen. Narrator, Magnifier, and On-Screen Keyboard have historically been vectors for bypass techniques because they run with elevated privileges on the secure desktop. Microsoft has patched several of these over the years, but the accessibility-to-lock-screen trust model remains a structural weakness. Defenders should expect additional variants.

The lesson here is structural: any trusted lock-screen component that can interact with user-writable configuration or reach external services is a candidate for bypass. Treat the lock screen as an exposed surface, not a sealed boundary.

Shield53 Recommendations

Shield53 Recommendations
Enable BitLocker pre-boot PIN immediately on all laptops and any machine that could physically leave controlled space. This is the single most effective mitigation: a reboot required to exploit FastUnlock against a PIN-protected machine leaves the disk encrypted.
Disable or restrict lock-screen accessibility tools where they are not needed, particularly Narrator, via Group Policy under Computer Configuration > Administrative Templates > Windows Components > Ease of Access.
Remove Microsoft account recovery options from lock screens on shared or kiosk-style devices. Local accounts with no lock-screen recovery path eliminate one prerequisite for the technique.
Enforce shutdown or hibernate policies for devices leaving user control. Sleep does not require re-authentication at boot, leaving the disk unlocked. Hibernate forces a TPM re-seal if a PIN is configured.
Deploy application allow-listing (e.g., WDAC, AppLocker, or a third-party solution like ThreatLocker itself) so that even if code executes from WSIAccount, only approved binaries run.
Monitor for anomalous WSIAccount activity in event logs. Any process creation or network connection originating from this account on a device that should be idle is a detection signal worth alerting on.
Physically secure shared and front-counter devices with cable locks, locked enclosures, or supervised access. Physical access is the root prerequisite — remove it and the technique is inert.

No official CVE or vendor advisory has been published at the time of this analysis. Treat all Windows versions meeting the described conditions as potentially affected until Microsoft issues guidance. We will update this commentary as additional details emerge.