A new unpatched zero-day vulnerability, termed FastUnlock, enables individuals with physical access to a locked Windows computer to execute programs without authentication.
Organizations utilizing Windows operating systems with physical access vulnerabilities are at risk, particularly where endpoint security measures are inadequate.
This vulnerability poses a significant risk as it allows unauthorized actions on secured devices, potentially leading to data breaches or further exploitation.
- Implement physical security measures for sensitive devices.
- Restrict access to locked systems to trusted personnel.
- Monitor system logs for unauthorized access attempts.
Key Technical Findings
Unpatched Windows 0-Day vulnerability – FastUnlock.
Windows operating systems (exact version range not specified).
Physical access to the locked system.
Execution of applications without user authentication.
Not specified in the source material.
Limited user access without administrative privileges.
Bypassing the login screen through physical access.
Not applicable; no credential theft involved.
Not applicable; local execution only.
Not specified in the source material.
Potential for unauthorized application execution leading to further exploits or data breaches.
Technical Background
The FastUnlock technique exploits the ability to execute applications on a locked Windows system, effectively bypassing the need for user authentication. This vulnerability is particularly concerning as it can be utilized by anyone with physical access to the machine, presenting a significant security gap for organizations that rely solely on password protection for device security.
The typical attacker objective in leveraging this vulnerability would be to execute malicious applications or scripts that could lead to further exploitation, such as lateral movement within a network or data exfiltration. Given that no actual privileges are escalated beyond a limited user account, the immediate impact may seem mitigated; however, the potential for follow-on attacks remains substantial.
Attack Chain Analysis
-
Initial Access
ActivityPhysical access to a locked Windows computer is gained.
EvidenceObservation of unauthorized individuals accessing devices in restricted areas.
TelemetryAccess logs indicating entries by unknown or unauthorized users.
Detection opportunityImplement alerts for physical access to sensitive devices.
-
Execution
ActivityExecution of applications without signing in.
EvidenceLogs of executed applications during locked state.
TelemetrySystem event logs capturing application launches and user states.
Detection opportunityMonitor event logs for application execution during unauthorized states.
Deep Technical Behavior Analysis
Bypassing Authentication Mechanisms
The FastUnlock technique likely leverages existing system functionalities intended for legitimate use. It may exploit how Windows handles processes when locked, enabling execution without full authentication. The implication here is that attackers could utilize benign-looking applications to perform malicious activities, as security controls may not adequately differentiate between legitimate and harmful processes under these conditions. Potential—requires validation.
Potential Indicators of Malicious Activity
While specific IoCs were not mentioned in the source material, behaviors such as unexpected application launches or attempts to execute scripts during locked states could signal exploitation of this vulnerability. Monitoring these behaviors can aid in detection efforts. Potential—requires validation.
Indicators of Compromise
Indicators of Behavior
| Behavioral Indicator | Description | Data Source | Confidence |
|---|---|---|---|
| Unauthorized Application Execution | Applications executing while the system is in a locked state. | System event logs | Potential |
Detection Engineering Guidance
index=edr event_type=
Recommended Log Sources
Platform
Log Source
What to Look For
Priority
Windows
Security Event Log
Logon (4624/4625), service (7045), task (4698), log clear (1102)
High
Windows
Sysmon
Process creation (1), network (3), image load (7), LSASS access (10)
High
Windows
PowerShell Operational
Script block logging (4104), module logging
High
Endpoint
EDR / Defender telemetry
Process tree, persistence, tamper attempts
High
Identity
IdP / VPN logs
Impossible travel, spraying, MFA fatigue
High
Network
DNS resolver logs
Rare/high-entropy domains, tunneling
Medium
Network
Proxy / firewall logs
Beaconing, direct-IP C2, exfil volume
High
MITRE ATT&CK Mapping
Not specified in the source material. Map techniques from confirmed telemetry before operationalising.
Incident Response Guidance
- Validate exposure and confirm whether the issue applies to your environment.
- Preserve evidence (memory, disk, relevant logs) before remediation.
- Isolate affected hosts/accounts if compromise is suspected.
- Collect volatile data and review the log sources listed above.
- Hunt for the indicators of behavior and any related atomic indicators.
- Rotate potentially exposed credentials, keys, and session tokens.
- Remove persistence (tasks, services, keys, web shells, cron, OAuth grants).
- Patch affected systems; reimage where integrity cannot be assured.
- Run post-remediation validation and a BAS/security-validation retest.
Remediation and Hardening
- Patch affected systems and reduce internet-exposed services.
- Enforce MFA and least-privilege for privileged and remote access.
- Improve endpoint telemetry (Sysmon/EDR) and PowerShell logging.
- Restrict script execution and constrain LOLBins where feasible.
- Monitor persistence locations and disable unnecessary services.
- Segment critical assets and review privileged accounts.
- Rotate secrets and remove credentials from configuration files.
- Tune SIEM/EDR detections, then validate controls after changes.
Business Risk
- Service disruption: degraded or unavailable systems during compromise or recovery.
- Data exposure: risk to sensitive, regulated, or customer data depending on scope.
- Regulatory exposure: potential breach-notification and compliance obligations.
- Financial impact: incident response, downtime, and potential extortion costs.
- Brand and trust impact: reputational damage with customers and partners.
- Identity blast radius: compromised accounts can expand access across cloud and SaaS.
Executive Takeaway
What leadership needs to know: Reducing exposure and improving detection coverage limits impact. Current assessed risk: Not specified.
Prioritise: patching/exposure reduction, identity hardening (MFA, least privilege), and detection coverage for the techniques above.
Validate after remediation: re-test controls with breach & attack simulation to confirm the relevant techniques are now prevented or detected.
Validate your defenses against this attack
The techniques in this article map directly to Valitrix validation modules — test your own controls against them:
- Endpoint Security Validation
Verify your EDR, XDR and AV controls actually detect the endpoint techniques used by this threat.
- SIEM Validation
Confirm your SIEM and detection rules fire on the attack behaviors covered in this article.
- BAS testing
Safely replay the same attack techniques against your own environment — non-disruptive and evidence-based.
Written by
Valitrix
Valitrix writes for Valitrix on continuous Breach and Attack Simulation, MITRE ATT&CK-aligned validation, and hardening security controls across endpoint, email, and network surfaces.



