A new, unpatched zero-day vulnerability in Microsoft Windows, named "FastUnlock," has been publicly disclosed by a security researcher. The flaw allows an attacker with physical access to a locked but running computer to bypass the lock screen and execute arbitrary programs. The technique, confirmed by endpoint security firm ThreatLocker, leverages a combination of the Windows Narrator accessibility tool and Microsoft account recovery options. This vulnerability poses a significant physical security risk, as it can undermine the protection offered by the lock screen, even on some systems using BitLocker drive encryption.
The vulnerability, disclosed by researcher 'Chaotic Eclipse' on November 19, 2026, does not require any special tools and can reportedly be executed in under five minutes. The attack chain involves:
The programs are executed with the restricted privileges of the WsiAccount (Windows Services for Sign-In account), not as a local administrator. However, this level of access is still sufficient to install malware, access user data on an unlocked volume, or establish persistence.
For the attack to work, the device must have at least one user account linked to an online Microsoft account, and the attacker needs physical access.
A proof-of-concept has been publicly disclosed by the researcher. As of November 20, 2026, Microsoft has not released a patch, and there is no evidence of active in-the-wild exploitation. However, the public nature of the disclosure increases the risk of adoption by malicious actors.
The primary risk is from device theft. A thief who steals a locked laptop (e.g., from a coffee shop or car) could use this technique to gain access to the data on the device, even if the user believes it is protected by their password and disk encryption. While the attacker does not gain administrative privileges directly, access as WsiAccount can be leveraged to:
The following patterns may help identify systems where this technique has been used post-compromise:
Narrator.exeWsiAccountWsiAccount user context that are not part of the normal sign-in process (e.g., cmd.exe, powershell.exe).WsiAccount followed by unexpected process creation events (ID 4688) could be an indicator.Detection of an active attempt is difficult as it requires physical presence. Post-incident forensic analysis is the most likely method of discovery.
Event ID 4688) originating from parent processes associated with the lock screen or WsiAccount.Narrator.exe spawning cmd.exe would be highly anomalous.As there is no patch available, mitigation relies on hardening system configurations and user behavior.
CRITICAL MITIGATION: The most effective countermeasure is to enable a pre-boot authentication PIN for BitLocker. This requires the user to enter a PIN before the operating system starts to load, ensuring the drive remains encrypted until the correct PIN is provided. This completely negates the FastUnlock vulnerability, as the OS and user data are inaccessible at the lock screen stage.
Additional Mitigations:
Enforcing a pre-boot authentication PIN for BitLocker is a configuration change that fully mitigates this threat.
Educating users to fully shut down or hibernate devices in untrusted environments reduces the window of opportunity for attackers.
The 'FastUnlock' zero-day vulnerability was publicly disclosed by researcher Chaotic Eclipse.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.