Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged local user
-
DeliveryTrigger concurrent Credential Manager operations
-
ExploitWin race-condition timing window
-
ExecutionExecute code as SYSTEM
-
ImpactFull local host compromise
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 target Windows host as at least a low-privileged user (PR:L, AV:L) - this is not remotely reachable. The core prerequisite is triggering concurrent execution against the shared resource in Windows Credential Manager and winning an improperly synchronized timing window (CWE-362), which the CVSS AC:H rating and SSVC Automatable=no confirm is non-deterministic and may require many attempts. Limiting factors that reduce real-world risk: the attacker needs an existing foothold/valid credentials on the machine, no remote or unauthenticated path exists, and success depends on winning a race rather than a reliable single-shot trigger; there is no public exploit and CISA SSVC reports no observed exploitation. |
| Impact | This is a credible but second-tier priority, not an emergency. The CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.0 HIGH) describes a local, already-authenticated attacker (PR:L) who must win a race condition (AC:H) to gain full confidentiality, integrity, and availability impact on the host - a classic privilege-escalation-to-SYSTEM profile. The exploitation signals argue AGAINST urgency and are internally consistent: CISA SSVC lists Exploitation=none and Automatable=no, there is no CISA KEV listing, and no public exploit identified at time of analysis, so this should be treated as 'no public exploit identified at time of analysis' rather than active threat. The one counter-signal is SSVC Technical Impact=total, which aligns with the triple-High impact and means a successful win yields complete control - so while the probability is low, the consequence is maximal. No EPSS score was provided in the input, so probabilistic exploitation likelihood cannot be quantified here. Net: a real, patch-worthy local EoP suitable for normal-to-prioritized monthly patching, elevated on multi-user/terminal-server hosts, but AC:H plus Automatable=no make reliable, scalable exploitation unlikely in the near term. |
| Exploit ScenarioDerived | A low-privileged but authenticated local user (or malware already running in a standard user context) repeatedly triggers concurrent Windows Credential Manager operations to hit a narrow timing window in an improperly synchronized shared resource. By winning that race, the attacker corrupts privileged state and elevates to SYSTEM, gaining full control of the host. No public exploit code is known, and the high attack complexity (AC:H) means exploitation requires repeated attempts to win the race. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Local privilege escalation in Windows Credential Manager affects Windows 10, Windows 11, and Windows Server (2012 through 2025) builds, letting an attacker who already holds a low-privileged local session on the host win a race condition (CWE-362) and elevate to higher privileges. The vulnerable component is not remotely reachable and the high attack complexity rating reflects a non-deterministic timing window that may require repeated attempts; exploitation requires authenticated local access (CVSS vector PR:L/AV:L), and no public exploit identified at time of analysis, with CISA SSVC recording no observed exploitation. Microsoft has published updated builds that correct the synchronization flaw, so remediation is a matter of patching rather than emergency mitigation.
RemediationAI
Patch available per vendor advisory: Microsoft has published updated Windows builds that resolve the Credential Manager race, with the EUVD-2026-99886 data identifying corrected build thresholds at the top of each affected range, including 6.2.9200.26434 for Server 2012, 6.3.9600.23470 for Server 2012 R2, 10.0.14393.9612 for Windows 10 1607 and Server 2016, 10.0.17763.9376 for Windows 10 1809 and Server 2019, 10.0.19044.7807 for Windows 10 21H2/22H2, 10.0.20348.5761 for Server 2022, 10.0.22631.7652 for Windows 11 23H2, 10.0.26100.9711 for Windows 11 24H2, 10.0.26100.33650 for Server 2025, and the corresponding thresholds for Windows 11 25H2, 26H1 and 26H2; consult and apply the updates listed at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69736. Because the defect is a timing race rather than a configurable feature, there is no single switch that removes the exposure reliably, so if patching must be staged, prioritize hosts where untrusted low-privileged code can run - multi-user Windows Server RDS/Citrix-style session hosts, jump boxes, and developer or build machines - and as compensating measures restrict interactive logon rights (RDP to local users, remove unnecessary local accounts and administrative shares) to shrink the set of principals who can attempt the race, and reduce the value of any leaked secret by deleting stale saved credentials from Credential Manager on shared systems, noting that this forces users to re-enter credentials and can break scheduled tasks, drive mappings and Windows Hello for Business convenience features that rely on the vault. Disabling the Credential Manager service outright is not a supported posture and will break Windows Hello, stored certificates and saved RDP credentials, so it should only be considered as a last resort on tightly managed, dedicated hosts. Detection should focus on unusual processes touching the vault or unexpectedly elevated child processes spawned from low-privileged contexts, paired with the fact that this is a local-only, non-automatable exploit (SSVC Exploitation=none, Automatable=no) with no public exploit identified at time of analysis, making it a second-tier priority behind externally reachable and actively exploited issues.
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 issue is a classic race condition (CWE-362), where concurrent execution against a shared resource in Windows Credential Manager occurs without proper synchronization, allowing state in the credential store to be manipulated in a way that yields elevated privileges for the local attacker. Credential Manager sits on top of the Windows Data Protection API and the Credential Vault service, and the affected CPEs span the Windows 10 (1607, 1809, 21H2, 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2) and Windows Server (2012, 2012 R2, 2016, 2019, 2022, 2025, including Server Core installations) product families, meaning the same core credential-storage code path is shared across client and server SKUs. The CVSS vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H indicates local vector, high attack complexity, and low privileges required, with high confidentiality and integrity impact within the same security scope. SSVC rates technical impact as total but automatable as no and exploitation as none, which aligns with a timing-dependent flaw that is difficult to trigger reliably and has not been observed in the wild; the accompanying tags (Information Disclosure, Race Condition, Microsoft) point to the credential-data exposure that can accompany the privilege-escalation primitive.
Know when Windows 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 authenticated foothold gives AV:L/PR:L; winning the race window is non-deterministic so AC:H; UI:N and S:U per description; escalation to SYSTEM yields C/I/A:H.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Credential Manager allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A privilege-escalation flaw in the Windows Credential Manager affects the full Windows endpoint and server estate - Windows 10, Windows 11, and Windows Server 2012 through 2025 - meaning nearly every managed host in the organization is exposed until patched. An attacker who already has a foothold on a machine could abuse the flaw to gain higher privileges and reach stored credentials, turning a minor local compromise into a broader credential and lateral-movement risk. Because Microsoft has already released corrected builds, this is a patch-hygiene obligation for IT operations rather than a crisis requiring emergency containment.
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).
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
EUVD-2026-99886
GHSA-h739-hgjw-3g66
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB