Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local low-privileged session
-
DeliveryRepeatedly invoke Microsoft Account operation
-
ExploitWin race-condition timing window
-
ExecutionCorrupt shared privileged resource
-
ImpactElevate to SYSTEM privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Concurrency control, locking
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to already have local, authenticated access to the Windows host with at least low-level privileges (PR:L) - this is not remotely reachable (AV:L). The core prerequisite is winning a race condition in the Microsoft Account component's unsynchronized access to a shared resource, which demands precise timing and typically many repeated attempts; this timing dependency (AC:H) is the primary limiting factor and makes reliable, automatable exploitation impractical (SSVC Automatable: no). No user interaction is required (UI:N). The flaw affects default Windows installations across the enumerated client and server builds, so no special non-default configuration is needed beyond standard local access. |
| Impact | This is a genuine but not top-tier priority. The CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N) describes a local attacker who already holds low-level privileges and must win a timing-sensitive race condition - the AC:H and AV:L metrics substantially constrain real-world exploitability, which is why the base score lands at 7.0 (High) rather than Critical despite full C:H/I:H/A:H impact. The SSVC decision framework reinforces a lower-urgency posture: Exploitation is rated 'none' (no observed or public exploitation), Automatable is 'no' (consistent with AC:H - a race cannot be reliably sprayed at scale), while Technical Impact is 'total' (consistent with the H/H/H impact set). There is no CISA KEV listing and no EPSS score was provided in the input, so probabilistic exploitation likelihood cannot be quantified here. All signals are mutually consistent and point the same direction: high technical impact if exploited, but meaningful difficulty (local access + privileges + timing) and no evidence of exploitation. Treat as a standard-cadence patch priority for the next Windows maintenance window rather than an emergency, with the caveat that the affected component (Microsoft Account) is present across the entire Windows fleet, so patch coverage must be broad. |
| Exploit ScenarioDerived | A local attacker who already has an unprivileged or standard authenticated session on a Windows host repeatedly triggers the vulnerable Microsoft Account operation to hit a narrow timing window in which a shared resource is accessed without proper synchronization. By winning that race, the attacker corrupts privileged state and elevates to SYSTEM-level control of the machine. No public exploit identified at time of analysis, and the high attack complexity (race condition) means exploitation typically requires many attempts rather than a single deterministic action. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Local privilege escalation in the Microsoft Account component shipped with default installations of Windows 10, Windows 11, and Windows Server 2012 through 2025 lets an attacker who already holds low-privileged local access to a host win a race condition and gain high-integrity code execution as SYSTEM. The flaw is a race condition (CWE-362) in which Microsoft Account code accesses a shared resource without proper synchronization; per the assessed vector (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) it is not remotely reachable, requires authenticated local access at PR:L, needs no user interaction, but is gated by high attack complexity because reliable exploitation depends on precise timing and typically many repeated attempts. There is no confirmed active exploitation and no public exploit identified at time of analysis, SSVC rates Automatable: no with total technical impact if the race is won, and vendor patches are available in the Microsoft security updates referenced by the MSRC advisory.
RemediationAI
Apply the vendor-released Microsoft security update for CVE-2026-85329 via Windows Update, WSUS, or the Microsoft Update Catalog using the build targets published in the MSRC advisory (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85329): Windows 10 21H2/22H2 to 10.0.19044.7807, Windows 10 1607 to 10.0.14393.9612, Windows 10 1809 to 10.0.17763.9376, Windows 11 23H2 to 10.0.22631.7652, Windows 11 24H2 to 10.0.26100.9711, Windows 11 25H2 to 10.0.26200.9711, Windows 11 26H1 to 10.0.28000.3231, Windows 11 26H2 to 10.0.26300.9711, Windows Server 2016 to 10.0.14393.9612, Windows Server 2019 to 10.0.17763.9376, Windows Server 2022 to 10.0.20348.5761, and Windows Server 2025 to 10.0.26100.33650; legacy Windows Server 2012 and 2012 R2 require 6.2.9200.26434 and 6.3.9600.23470 respectively and are only serviced under Extended Security Updates, so hosts without ESU must be migrated or isolated. Because exploitation requires pre-existing local low-privileged access, no network-side workaround blocks the issue; the effective compensating controls are reducing the local attack surface until patching is possible by removing unnecessary local accounts and interactive logon rights, enforcing least privilege and non-admin day-to-day accounts, using AppLocker or WDAC to constrain untrusted local binaries, and enabling Credential Guard and LSA protection to limit the payoff of a successful elevation. These controls carry operational trade-offs, since aggressive application-control policies can break line-of-business software and removing interactive logon rights can disrupt administrative workflows, and monitoring for repeated anomalous process starts or crash patterns in Microsoft Account related processes should be treated as a detection stopgap rather than a fix. There is no vendor-released standalone mitigation beyond the cumulative security update because the vulnerable code is part of the default identity stack.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 20 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-362, concurrent execution using a shared resource with improper synchronization, a classic race-condition/TOCTOU condition in the Microsoft Account (MSA) identity component of Windows. Microsoft Account functionality is deeply integrated into the Windows logon, token, and credential-management stack, and because the shared resource is accessed without adequate locking, a low-privileged local process can interleave operations in a narrow window and induce the privileged Microsoft Account code path to operate on state under attacker influence, escalating from low integrity to SYSTEM-level capabilities. The environment is local (AV:L) and the attacker must already be an authenticated low-privileged user (PR:L), with no user interaction required (UI:N); confidentiality, integrity, and availability impacts are all High, and CISA's SSVC decision framework rates technical impact as total while marking the issue non-automatable. The high attack complexity score (AC:H) reflects the timing dependency of the race: exploitation is plausible but probabilistic, requiring repeated attempts rather than a deterministic single-shot trigger, which is the primary constraint on weaponization. Because the affected code is part of default Windows installations across client and server SKUs, no non-default configuration is required beyond ordinary local access.
Know when Windows 10 1607 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Local-only race condition requires existing low privileges and precise timing, giving AV:L/PR:L/AC:H; successful exploitation yields full SYSTEM control so C/I/A all High.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Concurrent execution using shared resource with improper synchronization ('race condition') in Microsoft Account allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A high-severity local privilege escalation in Microsoft Windows (versions 10, 11, and Server 2012-2025) could allow an attacker with existing low-level access to gain SYSTEM-level control of affected systems. This poses a significant risk to organizations because a compromised user account could be leveraged to fully compromise hosts, move laterally, and access sensitive data. Patching is available and should be prioritized to mitigate this escalation path.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).
More in Windows 10 1607
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
EUVD-2026-99621
GHSA-xrpc-x228-55xg
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB