CVE-2026-44800
Received Received - Intake

BaseFortify

Vulnerability report for CVE-2026-44800, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-14

Last updated on: 2026-07-14

Assigner: Microsoft Corporation

Description

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-14
Last Modified
2026-07-14
Generated
2026-07-14
AI Q&A
2026-07-14
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
microsoft windows_push_notifications *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-44800 is a race condition vulnerability in Windows Push Notifications. A race condition occurs when multiple processes or threads access a shared resource without proper synchronization, leading to unpredictable behavior.

In this case, the vulnerability allows an authorized attacker with local access to exploit improper synchronization in the Windows Push Notifications component. This could enable the attacker to elevate their privileges on the affected system.

Impact Analysis

If exploited, this vulnerability could have the following impacts:

  • An attacker with local access to your system could gain elevated privileges, allowing them to perform actions they would not normally be authorized to do.
  • Elevated privileges could enable the attacker to install malicious software, modify system configurations, or access sensitive data.
  • The attacker could potentially take full control of the affected system, leading to further compromise of connected systems or networks.
Compliance Impact

This vulnerability could impact compliance with common standards and regulations in the following ways:

  • GDPR: If the vulnerability leads to unauthorized access to personal data, it could result in a data breach. Organizations must report such breaches within 72 hours under GDPR, and failure to do so could lead to significant fines.
  • HIPAA: For organizations handling protected health information (PHI), exploitation of this vulnerability could lead to unauthorized access to PHI. This would constitute a breach under HIPAA, requiring notification and potentially resulting in penalties.
  • Other standards (e.g., ISO 27001, NIST): The vulnerability represents a failure to maintain proper access controls and system integrity, which are key requirements in these frameworks. Exploitation could indicate non-compliance with security best practices.
Mitigation Strategies

Apply the security update provided by Microsoft to address CVE-2026-44800. The update will patch the race condition in Windows Push Notifications that could allow privilege escalation.

To obtain the update, visit the Microsoft Security Response Center (MSRC) update guide for this CVE.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-44800. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart