CVE-2026-26167
Race Condition in Windows Push Notifications Enables Local Privilege Escalation
Publication date: 2026-04-14
Last updated on: 2026-04-24
Assigner: Microsoft Corporation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| microsoft | windows_10_1607 | to 10.0.14393.9060 (exc) |
| microsoft | windows_10_1607 | to 10.0.14393.9060 (exc) |
| microsoft | windows_10_1809 | to 10.0.17763.8644 (exc) |
| microsoft | windows_10_1809 | to 10.0.17763.8644 (exc) |
| microsoft | windows_10_21h2 | to 10.0.19044.7184 (exc) |
| microsoft | windows_10_21h2 | to 10.0.19044.7184 (exc) |
| microsoft | windows_10_21h2 | to 10.0.19044.7184 (exc) |
| microsoft | windows_10_22h2 | to 10.0.19045.7184 (exc) |
| microsoft | windows_10_22h2 | to 10.0.19045.7184 (exc) |
| microsoft | windows_10_22h2 | to 10.0.19045.7184 (exc) |
| microsoft | windows_11_23h2 | to 10.0.22631.6936 (exc) |
| microsoft | windows_11_23h2 | to 10.0.22631.6936 (exc) |
| microsoft | windows_11_24h2 | to 10.0.26100.8246 (exc) |
| microsoft | windows_11_24h2 | to 10.0.26100.8246 (exc) |
| microsoft | windows_11_25h2 | to 10.0.26200.8246 (exc) |
| microsoft | windows_11_25h2 | to 10.0.26200.8246 (exc) |
| microsoft | windows_11_26h1 | to 10.0.28000.1836 (exc) |
| microsoft | windows_11_26h1 | to 10.0.28000.1836 (exc) |
| microsoft | windows_server_2016 | to 10.0.14393.9060 (exc) |
| microsoft | windows_server_2019 | to 10.0.17763.8644 (exc) |
| microsoft | windows_server_2022 | to 10.0.20348.5020 (exc) |
| microsoft | windows_server_2022_23h2 | to 10.0.25398.2274 (exc) |
| microsoft | windows_server_2025 | to 10.0.26100.32690 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | 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. |
| CWE-362 | The product contains a concurrent code sequence that 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 operating concurrently. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
This vulnerability involves a race condition in Windows Push Notifications that allows local privilege escalation.
To mitigate this vulnerability, it is recommended to apply the security updates provided by Microsoft as soon as they become available.
How can this vulnerability impact me? :
The vulnerability can allow an authorized attacker to elevate their privileges on the local system. This means the attacker could gain higher-level access rights than intended, potentially leading to full control over the affected Windows system.
Can you explain this vulnerability to me?
This vulnerability is a race condition in Windows Push Notifications where concurrent execution using a shared resource occurs without proper synchronization. This flaw allows an authorized attacker to elevate their privileges locally on the affected system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows an authorized attacker to elevate privileges locally through a race condition in Windows Push Notifications. Such elevation of privilege can potentially lead to unauthorized access or modification of sensitive data.
While the provided information does not explicitly mention compliance with standards like GDPR or HIPAA, privilege escalation vulnerabilities generally pose risks to data confidentiality, integrity, and availability, which are critical aspects of these regulations.
Organizations affected by this vulnerability should consider its impact on their security posture and compliance requirements, as exploitation could lead to breaches of protected data governed by such standards.