CVE-2026-27911
7.8
Vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Exploitability: 1.1 / Impact: 6.0
Source: secure@microsoft.com (Secondary)
Description
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows User Interface Core allows an authorized attacker to elevate privileges locally.
Affected (23)
Configuration A
| Vulnerable Software | Affected Versions |
|---|---|
| Before 10.0.14393.9060 | |
| Before 10.0.17763.8644 | |
| Before 10.0.19044.7184 | |
| Before 10.0.19045.7184 | |
| Before 10.0.22631.6936 | |
| Before 10.0.26100.8246 | |
| Before 10.0.26200.8246 | |
| Before 10.0.28000.1836 | |
| Before 10.0.14393.9060 | |
| Before 10.0.17763.8644 | |
| Before 10.0.20348.5020 | |
| Before 10.0.25398.2274 | |
| Before 10.0.26100.32690 |
Related CWEs
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently.
CWE-416
Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
References (1)
Source: secure@microsoft.com
Vendor Advisory
Timeline
No history available yet.