Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privilege user
  2. Exploit
    Identify unprotected shared resource in UI Core
  3. Execution
    Trigger concurrent access race condition
  4. Impact
    Achieve privilege escalation to system level

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

Local system access as authenticated user required. Windows User Interface Core must process concurrent requests on shared resources without proper synchronization. High attack complexity due to race condition timing requirements.

Impact

Real-world risk is moderate-to-high for privileged endpoint environments. CVSS 7.8 reflects local attack vector requiring low privileges (PR:L) but high attack complexity (AC:H), indicating successful exploitation demands precise timing manipulation. The scope change (S:C) confirms privilege boundary escape from user to SYSTEM context. EPSS data not provided, but race condition exploitation historically requires specialized tooling and system-specific tuning, reducing mass exploitation likelihood compared to memory corruption flaws. No confirmed actively exploited (CISA KEV) status and no public exploit identified at time of analysis lower immediate urgency. However, the comprehensive version coverage (all supported Windows client/server OS) and potential for lateral movement post-compromise in enterprise networks elevate priority. Patch available per vendor advisory mitigates deployment friction. Organizations should prioritize patching on high-value assets, privileged access workstations, and multi-tenant systems where local user accounts exist. The AC:H rating suggests automated exploitation at scale is unlikely, favoring targeted manual attacks.

Exploit ScenarioDerived

An attacker with standard user credentials on a corporate Windows 10 workstation executes a custom exploit tool that rapidly creates and destroys UI window objects while monitoring kernel object handles. By precisely timing thread execution to exploit the race window in User Interface Core's synchronization logic, the attacker manipulates the UI subsystem to assign SYSTEM-level privileges to their user session token during a state transition. With

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 14, 2026

Race condition in Windows User Interface Core (MSRC patch CVE-2026-27911) enables low-privileged authenticated attackers to elevate privileges to SYSTEM level on Windows 10, Windows 11, and Windows Server 2016-2025 systems. The flaw stems from improper synchronization when multiple threads concurrently access shared resources in the UI subsystem, creating a time-of-check-time-of-use (TOCTOU) window exploitable for privilege escalation. Patch available per vendor advisory. No public exploit ident

Earlier versions of this analysis (1)
v1 Apr 14, 2026 - 19:29 CVSS 7.8

Race condition in Windows User Interface Core (MSRC patch CVE-2026-27911) enables low-privileged authenticated attackers to elevate privileges to SYSTEM level on Windows 10, Windows 11, and Windows Server 2016-2025 systems. The flaw stems from improper synchronization when multiple threads concurrently access shared resources in the UI subsystem, creating a time-of-check-time-of-use (TOCTOU) window exploitable for privilege escalation. Patch available per vendor advisory. No public exploit identified at time of analysis. CVSS 7.8 (high complexity, scope change possible), targeting broad Windows deployment base including all supported Windows 10/11 and Server editions.

RemediationAI

Apply the vendor-released patches immediately from Microsoft Security Response Center. Upgrade Windows 10 Version 1607 to build 10.0.14393.9060 or later, Version 1809 to 10.0.17763.8644+, Version 21H2 to 10.0.19044.7184+, and Version 22H2 to 10.0.19045.7184+. For Windows 11, upgrade 22H3/23H2 to build 10.0.22631.6936+, 24H2 to 10.0.26100.32690+, 25H2 to 10.0.26200.8246+, and 26H1 to 10.0.28000.1836+. Server administrators must patch Server 2016 to 10.0.14393.9060+, Server 2019 to 10.0.17763.8644+, Server 2022 to 10.0.20348.5020+, Server 2022 23H2 Edition to 10.0.25398.2274+, and Server 2025 to 10.0.26100.32690+. Deploy patches via Windows Update, WSUS, or SCCM. No effective workarounds exist due to the kernel-level nature of the UI subsystem; patching is the only reliable mitigation. Detailed update guidance at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-27911.

Affected VersionsENISA

Windows 10 Version 1809 10.0.17763.0 <10.0.17763.8644
Windows Server 2025 10.0.26100.0 <10.0.26100.32690
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9060
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.6936
Windows 11 version 22H3 10.0.22631.0 <10.0.22631.6936
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9060
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.8644
Windows Server 2022 10.0.20348.0 <10.0.20348.5020
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.32690
Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7184
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.8246
Windows Server 2019 10.0.17763.0 <10.0.17763.8644
Windows Server 2016 10.0.14393.0 <10.0.14393.9060
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.1836
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7184
Windows Server 2022, 23H2 Edition (Server Core installation) 10.0.25398.0 <10.0.25398.2274
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.32690

Affected Packages

microsoft windows_10_version_1607_10_0_14393_9060 fix: Windows 10 Version 1607 for 32-bit Systems 10.0.14393.9060, Windows 10 Version 1607 for x64-based Systems 10.0.14393.9060
microsoft windows_10_version_1809_10_0_17763_8644 fix: Windows 10 Version 1809 for 32-bit Systems 10.0.17763.8644, Windows 10 Version 1809 for x64-based Systems 10.0.17763.8644
microsoft windows_10_version_21h2_10_0_19044_7184 fix: Windows 10 Version 21H2 for 32-bit Systems 10.0.19044.7184, Windows 10 Version 21H2 for ARM64-based Systems 10.0.19044.7184, Windows 10 Version 21H2 for x64-based Systems 10.0.19044.7184
microsoft windows_10_version_22h2_10_0_19045_7184 fix: Windows 10 Version 22H2 for 32-bit Systems 10.0.19045.7184, Windows 10 Version 22H2 for ARM64-based Systems 10.0.19045.7184, Windows 10 Version 22H2 for x64-based Systems 10.0.19045.7184
microsoft windows_11_version_23h2_10_0_22631_6936 fix: Windows 11 Version 23H2 for ARM64-based Systems 10.0.22631.6936, Windows 11 Version 23H2 for x64-based Systems 10.0.22631.6936
microsoft windows_11_version_24h2_10_0_26100_32690 fix: Windows 11 Version 24H2 for ARM64-based Systems 10.0.26100.32690, Windows 11 Version 24H2 for x64-based Systems 10.0.26100.32690
microsoft windows_11_version_25h2_10_0_26200_8246 fix: Windows 11 Version 25H2 for ARM systems 10.0.26200.8246, Windows 11 Version 25H2 for x64-based Systems 10.0.26200.8246
microsoft windows_11_version_26h1_10_0_28000_1836 fix: Windows 11 Version 26H1 for ARM64-based Systems 10.0.28000.1836, Windows 11 version 26H1 for x64-based Systems 10.0.28000.1836
microsoft windows_server_2016_10_0_14393_9060 fix: Windows Server 2016 10.0.14393.9060, Windows Server 2016 (Server Core installation) 10.0.14393.9060
microsoft windows_server_2019_10_0_17763_8644 fix: Windows Server 2019 10.0.17763.8644, Windows Server 2019 (Server Core installation) 10.0.17763.8644
microsoft windows_server_2022_10_0_20348_5020 fix: Windows Server 2022 10.0.20348.5020, Windows Server 2022 (Server Core installation) 10.0.20348.5020
microsoft windows_server_2022_23h2_edition_10_0_25398_2274 fix: Windows Server 2022, 23H2 Edition (Server Core installation) 10.0.25398.2274
microsoft windows_server_2025_10_0_26100_32690 fix: Windows Server 2025 10.0.26100.32690, Windows Server 2025 (Server Core installation) 10.0.26100.32690
euvd windows_10_version_1607 fix: 10.0.14393.9060
euvd windows_10_version_1809 fix: 10.0.17763.8644
euvd windows_10_version_21h2 fix: 10.0.19044.7184
euvd windows_10_version_22h2 fix: 10.0.19045.7184
euvd windows_11_version_22h3 fix: 10.0.22631.6936
euvd windows_11_version_23h2 fix: 10.0.22631.6936
euvd windows_11_version_24h2 fix: 10.0.26100.32690
euvd windows_11_version_25h2 fix: 10.0.26200.8246
euvd windows_11_version_26h1 fix: 10.0.28000.1836
euvd windows_server_2016 fix: 10.0.14393.9060
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9060
euvd windows_server_2019 fix: 10.0.17763.8644
euvd windows_server_2019_server_core_installation fix: 10.0.17763.8644
euvd windows_server_2022 fix: 10.0.20348.5020
euvd windows_server_2022_23h2_edition_server_core_installation fix: 10.0.25398.2274
euvd windows_server_2025 fix: 10.0.26100.32690
euvd windows_server_2025_server_core_installation fix: 10.0.26100.32690

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 30 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 vulnerability resides in the Windows User Interface Core component, a fundamental subsystem managing window creation, message handling, and UI resource allocation. CWE-362 (race condition) indicates the flaw occurs when multiple execution threads access shared kernel objects or memory structures without proper locking mechanisms, creating a TOCTOU vulnerability. During UI operations requiring state transitions, an attacker with low-privilege local access can manipulate timing to win the race between permission checks and resource allocation, bypassing security boundaries. Affected CPE strings span Windows 10 (versions 1607/1809/21H2/22H2), Windows 11 (22H3/23H2/24H2/25H2/26H1), and Windows Server 2016/2019/2022/2025 including Server Core installations, representing kernel-level UI infrastructure shared across all modern Windows versions since build 10.0.14393.0.

Know when Windows Server 2016 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

Vendor (microsoft) PRIMARY 7.8 HIGH
AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
CIRCL (temporal) 6.8 MEDIUM

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch released
Apr 14, 2026 - 17:46 nvd
Patch available
CVE Published
Apr 14, 2026 - 16:58 nvd
HIGH 7.8

DescriptionCVE.org

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows User Interface Core allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

CVE-2026-27911 is a Windows privilege escalation vulnerability affecting Windows 10, Windows 11, and Server 2016-2025 that allows authenticated users to gain SYSTEM-level access through a race condition in the UI subsystem. This poses significant risk to organizational Windows fleets, as any authenticated user-including those with minimal privileges-can escalate to administrator level, potentially enabling lateral movement, data exfiltration, and system compromise across the environment.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.0%
Top 89% exploitable
Vendor Action
See Below
Required. The vulnerability documented by this CVE requires customer action to resolve.
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Unlikely
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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).

CVE-2021-40444 HIGH POC
8.8 Sep 15

Windows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX

CVE-2021-34527 HIGH POC
8.8 Jul 02

<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi

CVE-2022-30190 HIGH POC
7.8 Jun 01

Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f

CVE-2017-0147 HIGH POC
7.5 Mar 17

The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows

CVE-2018-8174 HIGH POC
7.5 May 09

The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co

CVE-2021-1675 HIGH POC
7.8 Jun 08

Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth

CVE-2016-7255 HIGH POC
7.8 Nov 10

The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited

CVE-2023-36884 HIGH POC
7.5 Jul 11

Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2024-30088 HIGH POC
7.0 Jun 11

Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR

CVE-2019-1458 HIGH POC
7.8 Dec 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2018-8453 HIGH POC
7.8 Oct 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy