Skip to main content

Windows Push Notifications CVE-2026-70198

| EUVDEUVD-2026-99189 HIGH
Use After Free (CWE-416)
2026-10-13 secure@microsoft.com GHSA-4c77-g3xx-32c4
7.0
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

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

  1. Access
    Obtain low-privileged local session
  2. Delivery
    Interact with Windows Push Notifications component
  3. Exploit
    Trigger use-after-free and win race
  4. Execution
    Reuse freed object to corrupt memory
  5. Impact
    Execute code at elevated privilege

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK

2 techniques across 2 tactics: Execution, 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 the attacker to already hold a low-privileged authenticated local session on the Windows host (PR:L, AV:L) - there is no remote or unauthenticated path. The attacker must interact with the Windows Push Notifications subsystem and successfully win a race condition to reuse freed memory; the AC:H rating indicates this timing-dependent use-after-free is not reliably triggered and may require repeated attempts. Limiting factors that reduce real-world risk: mandatory prior local access, the race-condition dependency, no user interaction of a victim is needed (UI:N) but the attacker-side reliability is low, and the flaw affects only the enumerated vulnerable Windows build ranges - patched builds listed in the EUVD advisory are not exploitable.

Impact

This is a genuine but not top-priority issue. The CVSS vector (AV:L/AC:H/PR:L/UI:N/S:U) confirms this is a local privilege-escalation flaw requiring the attacker to already have low-level authenticated access to the host and to win a race condition (AC:H), which materially lowers reliability of exploitation despite the high C:H/I:H/A:H impact. No EPSS score, SSVC decision data, or POC indicator was provided in the input, and the CVE is NOT listed in CISA KEV, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The 7.0 base score is driven by full CIA impact after a successful local exploit, not by ease of reach - the AC:H and PR:L constraints mean this is a realistic post-compromise escalation primitive rather than an internet-facing emergency. Note a signal tension: the input Tags include 'Denial Of Service' while the description and vector describe privilege elevation with full integrity/confidentiality impact - a use-after-free can plausibly cause both, but treat the DoS label as secondary to the stated EoP outcome. Prioritize patching on multi-user, shared, or attacker-reachable Windows hosts where an unprivileged foothold is plausible.

Exploit ScenarioDerived

An attacker who already has a low-privileged authenticated session on a Windows host (e.g., a standard user, a compromised service account, or malware run as a normal user) triggers a use-after-free in the Windows Push Notifications component by racing freed-object reuse to corrupt memory. Winning the race lets them execute code in a higher-privileged context, elevating from standard user toward SYSTEM. No public proof-of-concept was identified in the provided data, and the AC:H race condition makes exploitation non-trivial but feasible with repeated attempts.

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

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

Alert me

AnalysisAIv1 – Oct 14, 2026

Local privilege escalation in Windows Push Notifications allows an attacker who already holds a low-privileged authenticated local session to gain SYSTEM-level code execution by exploiting a timing-dependent use-after-free (CWE-416), but the high complexity score (AC:H) and race-condition requirement make successful exploitation unreliable. Microsoft has released patches, and no public exploit has been identified at time of analysis. The flaw scores 7.0 CVSS and can lead to full confidentiality, integrity, and availability impact, yet the mandatory local access prerequisite makes it a genuine but not top-priority issue.

RemediationAI

Apply the Microsoft update for CVE-2026-70198 via Windows Update or the MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70198). For each affected version, the fixed build is the upper bound of the affected range: Windows 11 24H2 ≥ 10.0.26100.9711, Windows 11 25H2 ≥ 10.0.26200.9711, Windows 11 23H2 ≥ 10.0.22631.7652, Windows 11 26H1 ≥ 10.0.28000.3231, Windows 11 26H2 ≥ 10.0.26300.9711, Windows 10 1809 and Server 2019 ≥ 10.0.17763.9376, Windows 10 21H2 ≥ 10.0.19044.7807, Windows Server 2022 ≥ 10.0.20348.5761, and Windows Server 2025 ≥ 10.0.26100.33650. Windows 10 22H2 users should consult the MSRC advisory for the correct fixed build, as the EUVD range for that version appears inconsistent. If patching must be delayed, restrict local interactive logon to trusted users (since the vulnerability requires an existing low-privileged session) and monitor for unusual crashes in the Push Notifications service, but these measures are only compensating controls and do not eliminate the risk.

Affected VersionsENISA

Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows 10 Version 22H2 10.0.19045.0 <10.0.19044.7807
Windows Server 2019 10.0.17763.0 <10.0.17763.9376
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7807
Windows Server 2022 10.0.20348.0 <10.0.20348.5761
Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652

Affected Packages

euvd windows_10_version_1809 fix: 10.0.17763.9376
euvd windows_10_version_21h2 fix: 10.0.19044.7807
euvd windows_10_version_22h2 fix: 10.0.19044.7807
euvd windows_11_version_23h2 fix: 10.0.22631.7652
euvd windows_11_version_24h2 fix: 10.0.26100.9711
euvd windows_11_version_25h2 fix: 10.0.26200.9711
euvd windows_11_version_26h1 fix: 10.0.28000.3231
euvd windows_11_version_26h2 fix: 10.0.26300.9711
euvd windows_server_2019 fix: 10.0.17763.9376
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9376
euvd windows_server_2022 fix: 10.0.20348.5761
euvd windows_server_2025 fix: 10.0.26100.33650
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33650

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 13 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is a use-after-free (CWE-416) in the Windows Push Notifications subsystem, a user-mode component that manages notification delivery and interaction with the Windows Notification Platform. A use-after-free occurs when memory is freed but a pointer to it is subsequently dereferenced, allowing an attacker to influence the reallocation of that memory and potentially execute arbitrary code in the context of the component. In this case, the flaw requires a local attacker with low privileges (PR:L) to interact with the affected interface and win a race condition (AC:H) to trigger the reuse of the freed memory; no user interaction on the victim's part is required (UI:N). The affected builds span Windows 10, Windows 11 (versions 21H2 through 26H2), and Windows Server 2019, 2022, and 2025, as enumerated in the EUVD advisory. Successful exploitation elevates privileges to SYSTEM, giving full control over the host.

Know when the next one hits your stack

  • 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.0 HIGH
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.0 HIGH

Local-only use-after-free requiring an existing low-privilege session (AV:L/PR:L) and a timing race to trigger reuse (AC:H), yielding full code-execution impact (C/I/A:H).

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

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

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:19 cve.org
HIGH 7.0

DescriptionCVE.org

Use after free in Windows Push Notifications allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

Microsoft Windows Push Notifications is affected by a high-severity local privilege escalation vulnerability that could let an attacker with an existing low-privileged foothold on a Windows endpoint gain SYSTEM-level control of that machine. Although the race-condition requirement makes reliable exploitation difficult and no public exploit identified at time of analysis, a successful attack would expose full confidentiality, integrity, and availability impact on the affected host. Leadership should care because compromised endpoints could become a stepping stone for credential theft, lateral movement, and broader operational disruption, making timely patching of Windows systems a priority.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 82% exploitable
Prevalence
Ubiquitous
Core component of Windows desktop and server across all supported versions
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
5 sources
Confidence: Medium

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.3%
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
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

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

Attack Technique

Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

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