Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-87710 Overview
CVE-2026-87710 is a local privilege escalation vulnerability in the Microsoft Local Security Authority Server (lsasrv). Improper access control combined with a race condition weakness ([CWE-362]) allows an authorized local attacker to elevate privileges on an affected Windows system. Successful exploitation grants high impact to confidentiality, integrity, and availability.
The vulnerability requires local access and low privileges but no user interaction. Microsoft published the advisory on October 13, 2026, and no public exploit or in-the-wild activity has been reported at the time of writing.
Critical Impact
An authenticated local attacker who wins a race condition in lsasrv can elevate to higher privileges, compromising the integrity of credential material processed by the Local Security Authority Subsystem Service.
Affected Products
- Microsoft Windows (Local Security Authority Server component lsasrv)
- Specific affected builds listed in the Microsoft Security Update Guide
- Refer to the vendor advisory for the authoritative product and build matrix
Discovery Timeline
- 2026-10-13 - Microsoft published the security advisory for CVE-2026-87710
- 2026-10-13 - CVE-2026-87710 published to the National Vulnerability Database (NVD)
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-87710
Vulnerability Analysis
The flaw resides in the Local Security Authority Server (lsasrv), the user-mode component underpinning the Local Security Authority Subsystem Service (LSASS). LSASS enforces local security policy, validates logons, and manages authentication tokens. A defect in how lsasrv enforces access control during a time-sensitive operation permits an authorized local user to perform actions reserved for a higher-privilege context.
Because LSASS runs as a protected system component handling credential material and token issuance, successful exploitation can lead to arbitrary access to secrets held by the subsystem. The attack is local and requires valid credentials on the host, which limits remote exposure but makes the issue relevant for multi-user systems, Remote Desktop hosts, and Virtual Desktop Infrastructure.
Root Cause
The root cause is classified as a concurrent execution issue using shared resources with improper synchronization, commonly known as a race condition ([CWE-362]). The access control check and the privileged operation are not performed atomically. An attacker who interleaves operations between the check and the use can bypass the intended authorization boundary within lsasrv.
Attack Vector
The attack vector is local. An attacker must already hold a low-privilege account on the target host. The attack complexity is high, reflecting the timing precision required to win the race window. No user interaction is required, and the exploitation remains within a single security scope.
Exploitation typically involves repeatedly triggering the vulnerable code path in lsasrv while concurrently modifying the state the subsystem relies on for its authorization decision. On a successful race, the attacker gains elevated privileges, which can be used to extract credentials from LSASS memory, create new privileged accounts, or persist on the host.
No verified proof-of-concept code is publicly available. See the Microsoft Security Update Guide for vendor-authored technical details.
Detection Methods for CVE-2026-87710
Indicators of Compromise
- Unexpected child processes spawned by lsass.exe or anomalous threads injected into the LSASS process
- New local or domain accounts added shortly after a low-privilege logon session
- Access attempts to LSASS memory from non-system processes, including handle duplication to lsass.exe with PROCESS_VM_READ or PROCESS_QUERY_INFORMATION
- Repeated, high-frequency calls to LSA RPC interfaces originating from a single low-privilege session, consistent with race-condition exploitation attempts
Detection Strategies
- Enable Windows Defender Credential Guard where supported to isolate LSA secrets from user-mode access
- Monitor Sysmon Event ID 10 (ProcessAccess) targeting lsass.exe and correlate with the initiating user and process lineage
- Alert on Security Event ID 4672 (special privileges assigned) following a non-administrative logon from the same session
- Baseline normal lsasrv RPC call volumes and alert on sudden bursts from unprivileged sessions
Monitoring Recommendations
- Forward Windows Security, Sysmon, and PowerShell logs to a centralized analytics platform for correlation across hosts
- Track account creation, group membership changes, and privilege assignments in near real time
- Review endpoint behavioral telemetry for process access patterns consistent with LSASS credential theft tooling
How to Mitigate CVE-2026-87710
Immediate Actions Required
- Apply the Microsoft security update referenced in the Microsoft Security Update Guide to all affected Windows systems
- Prioritize patching on multi-user systems, Remote Desktop Session Hosts, VDI infrastructure, and jump hosts where local accounts are most prevalent
- Audit local account inventory and remove unnecessary interactive logon rights
- Validate that LSA Protection (RunAsPPL) and Credential Guard are enabled on supported systems
Patch Information
Microsoft released a security update addressing CVE-2026-87710 on October 13, 2026. Consult the Microsoft Security Update Guide for the KB article, affected product list, and build numbers specific to your Windows version. Install the update through Windows Update, WSUS, Microsoft Update Catalog, or your preferred patch management workflow.
Workarounds
- No vendor-supplied workaround has been published; patching is the authoritative remediation
- Restrict interactive logon on sensitive hosts to administrators only, reducing the pool of accounts capable of attempting local exploitation
- Enable LSA Protection (RunAsPPL) via the registry to limit non-protected process access to LSASS
- Enforce application allow-listing to block unapproved binaries that could stage the race condition exploit
# Enable LSA Protection (RunAsPPL) on Windows
# Requires reboot; verify driver compatibility before enterprise rollout
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Lsa" /v RunAsPPL /t REG_DWORD /d 1 /f
# Verify installed updates include the CVE-2026-87710 fix
wmic qfe list brief /format:table
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

