Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local account
-
DeliveryRun code invoking USB driver operations
-
ExploitRace the synchronization window
-
ExecutionCorrupt kernel object state
-
PersistEscalate to SYSTEM
-
ImpactDisable defenses or persist
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 local, authenticated access with low privileges already present on the host (CVSS PR:L, AV:L) - this is a post-compromise privilege escalation, not a remote entry point. The attacker must interact with the Windows USB driver and reliably win a timing-sensitive race condition; high attack complexity (AC:H) is the principal limiting factor, as the synchronization window is non-deterministic and typically demands many attempts. No user interaction is needed (UI:N). Practical exploitation is further constrained by needing the ability to invoke USB driver code paths on the target; environments that restrict USB usage or local code execution raise the bar. Only builds below the fixed versions on the listed Windows 10/11 and Server 2012-2025 editions are vulnerable. |
| Impact | Signals are consistent and point to a genuine-but-not-emergency priority. The CVSS 3.1 vector AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H (7.0, High) shows local-only access, high attack complexity (winning the race), and a requirement for existing low-level privileges - a meaningful barrier to opportunistic attackers. EPSS is low at 0.19% (9th percentile) and CISA SSVC marks Exploitation: none and Automatable: no, both reinforcing that this is not currently mass-exploited and is hard to reliably weaponize. Countervailing that, SSVC Technical Impact is 'total' and the CVSS impact metrics are C:H/I:H/A:H, meaning a successful exploit fully compromises the host. Note one data conflict: the description states privilege elevation while the intelligence Tags also list 'Information Disclosure' - the primary vendor-classified impact is local EoP, and the disclosure tag should be verified against the MSRC advisory. Net: patch on the normal expedited cycle for a local EoP; it is not a drop-everything internet-facing threat. |
| Exploit ScenarioDerived | A low-privileged user (or malware running in a standard user context after initial foothold) executes a small local program that repeatedly triggers USB driver operations to hit the synchronization window, racing to corrupt kernel state before the driver revalidates it. On a successful race the attacker gains kernel/SYSTEM privileges and can disable security tooling or install persistence. No public exploit is identified at time of analysis, and the high attack complexity (AC:H) means many attempts may be needed to win the race. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Jul 16, 2026
Local privilege escalation in the Microsoft Windows USB driver stack lets an already-authenticated low-privileged user win a race condition (CWE-362) to gain SYSTEM-level control across Windows 10 (1607-22H2), Windows 11 (24H2/25H2/26H1), and Windows Server 2012 through 2025. Reported by Microsoft with a patch available; there is no public exploit identified at time of analysis and it is not listed in CISA KEV. EPSS is low (0.19%, 9th percentile) and SSVC rates exploitation as none but technical impact as total, indicating high damage potential if a working exploit is developed.
Earlier versions of this analysis (1)
Local privilege escalation in the Microsoft Windows USB Driver (kernel-mode) lets an already-authenticated low-privileged user win a race condition (CWE-362) to elevate to SYSTEM. The flaw spans a broad Windows fleet from Windows 10 1607 through Windows 11 26H1 and Windows Server 2012 through Server 2025. No public exploit identified at time of analysis, and it is not listed in CISA KEV; a vendor patch is available from Microsoft.
RemediationAI
Patch available per vendor advisory - apply the Microsoft cumulative update that raises each build past the fixed threshold listed by MSRC/EUVD (for example Windows 11 24H2 to 10.0.26100.8875 or later, Windows Server 2025 to 10.0.26100.33158 or later, Windows 10 21H2/22H2 to 10.0.19044.7548/10.0.19045.7548, and Windows Server 2012 R2 to 6.3.9600.23291); confirm the exact KB and build for your edition at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50321. Because exploitation requires local low-privileged access and there is no vendor-published standalone workaround, interim compensating controls target that access path: enforce least privilege and strong endpoint access controls to limit who can run local code, and where USB is not operationally required, restrict USB device installation via Group Policy (Prevent installation of removable devices) - with the trade-off that this breaks legitimate USB peripherals and does not fully cover already-present device objects, so it is a stopgap, not a substitute for the update.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 32 packages in microsoft, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a concurrent-execution race condition (CWE-362) in the Windows USB driver - kernel-mode code that mediates enumeration and I/O for USB devices. Improper synchronization over a shared resource (e.g., a time-of-check-to-time-of-use window on a shared buffer or device object) allows a caller to manipulate state between validation and use, corrupting kernel memory or object references. Because USB handling runs in ring-0, successful exploitation yields code execution in the kernel context. The affected CPEs span the full modern Windows line: cpe:2.3:a:microsoft:windows_10_version_1607 through windows_11_version_26h1, plus Windows Server 2012, 2012 R2, 2016, 2019, 2022, and 2025 including Server Core installations, confirming this is core-OS driver code rather than an optional component.
Know when Windows Server 2012 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 post-auth escalation (AV:L/PR:L) gated by a hard-to-win race (AC:H), no user interaction, yielding full kernel compromise (C:H/I:H/A:H) within the same host (S:U).
Primary rating from Vendor (microsoft).
CVSS VectorNVD
Lifecycle Timeline
3DescriptionNVD
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows USB Driver allows an authorized attacker to elevate privileges locally.
Executive ViewAI
CVE-2026-50321 is a privilege escalation vulnerability affecting Windows 10, 11, and Server 2012-2025, allowing employees and contractors with local system access to gain administrator-level control. This exposure enables insider threats, lateral network movement, and compromise of critical business systems. Microsoft's patch is available and should be deployed immediately across your Windows infrastructure.
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 Server 2012
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
Remote code execution in Microsoft Office 2007-2016 and Windows Vista through 10 allows attackers to execute arbitrary c
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
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
Active Directory Domain Services Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.5), this vulnerabilit
EUVD-2026-43880
GHSA-pjvc-v637-5rjg
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB