Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged local user
-
ExploitTrigger use-after-free in Windows Error Reporting
-
ExecutionReclaim freed object and hijack execution
-
ImpactElevate to SYSTEM privileges
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 | Requires the attacker to already have local, authenticated access with low privileges on the Windows host (AV:L, PR:L) - there is no remote or unauthenticated path. Exploitation targets the Windows Error Reporting (WER) component via a use-after-free (CWE-416). The key limiting factor is high attack complexity (AC:H): a use-after-free elevation typically demands winning a race condition or precise heap grooming to reclaim the freed allocation, so exploitation is not reliable on a single attempt and is not automatable per SSVC. No user interaction is required (UI:N). Affected are specific unpatched build ranges across Windows 10/11 (including 23H2-26H2) and Windows Server 2012 through 2025; patched builds listed in the EUVD data are not vulnerable. |
| Impact | Signals are mixed and point to a genuine but non-urgent patching priority. The CVSS 3.1 base score is 7.0 (High) with vector AV:L/AC:H/PR:L/UI:N/S:U - meaning exploitation requires local access, an already-authenticated low-privileged account, AND a high-complexity precondition (AC:H), which for a CWE-416 use-after-free typically reflects winning a race or grooming the heap into a specific state. CISA SSVC reinforces the lower urgency: Exploitation=none (no observed exploitation) and Automatable=no, which is consistent with the AC:H rating, even though Technical Impact=total aligns with the C:H/I:H/A:H full-SYSTEM compromise outcome. No EPSS score was supplied, so quantitative exploitation probability cannot be stated. KEV status is not listed (not in CISA KEV) and no POC is indicated, so there is no public exploit identified at time of analysis. Net: this is a credible local privilege-escalation primitive that attackers value as a second-stage tool after initial foothold, but the local-only vector, authentication requirement, and high attack complexity make it a routine-priority patch rather than an emergency. Note one data tension to verify: the input Tags include 'Denial Of Service', yet the description and CVSS (C:H/I:H/A:H, elevation of privilege) describe a code-execution/EoP outcome, not a pure DoS - treat the DoS label with caution. |
| Exploit ScenarioDerived | An attacker who has already gained a low-privileged foothold on a Windows host (e.g., via phishing or a compromised standard user account) runs a crafted local program that manipulates Windows Error Reporting to trigger a use-after-free, then reclaims the freed memory to redirect execution and escalate to SYSTEM. Because CVSS specifies AC:H, the exploit must reliably win a timing/heap-grooming race, so success is not guaranteed on every attempt. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Local privilege escalation in Microsoft Windows Error Reporting (WER) allows an attacker who already holds low-privileged local access on a Windows host to elevate to higher integrity, and potentially to SYSTEM, by triggering a use-after-free during error-report handling. Only unpatched Windows 10/11 builds (23H2 through 26H2) and Windows Server 2012 through 2025 up to the build thresholds listed by Microsoft are affected; patched builds are not vulnerable. Exploitation requires authentication (CVSS PR:L) and is rated high complexity (AC:H) because the memory-reuse condition must be won reliably, which is consistent with CISA SSVC scoring of Autonomable: no - no public exploit code has been identified and there is no KEV listing, so the practical risk is a local, post-compromise escalation primitive rather than an urgent remote threat. A vendor patch is available.
RemediationAI
Apply the vendor-released patch: install the Microsoft security update referenced in the MSRC advisory for CVE-2026-83689 (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83689), which raises each affected edition to or above its fixed build - for example 10.0.22631.7652 for Windows 11 23H2, 10.0.26100.9711 for Windows 11 24H2, 10.0.26200.9711 for Windows 11 25H2, 10.0.28000.3231 for Windows 11 26H1, 10.0.26300.9711 for Windows 11 26H2, 10.0.19044.7807 for Windows 10 21H2/22H2, 10.0.17763.9376 for Windows 10 1809 and Server 2019, 10.0.14393.9612 for Windows 10 1607 and Server 2016, 10.0.20348.5761 for Windows Server 2022, 10.0.26100.33650 for Windows Server 2025, 6.2.9200.26434 for Windows Server 2012, and 6.3.9600.23470 for Windows Server 2012 R2. Because this is a local authenticated escalation (AV:L/PR:L) and not a remote or network-facing flaw, patching urgency is driven by how much untrusted low-privileged code already runs on the host - RDP/Citrix session hosts, multi-tenant jump boxes, and CI/build agents should be prioritized. If immediate patching is not possible, the most direct compensating control is to suppress WER data collection on hardened or high-value hosts by setting HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\Disabled = 1 (or via Group Policy under Computer Configuration > Administrative Templates > Windows Components > Windows Error Reporting), which removes the attack surface for this code path but has the trade-off of eliminating crash diagnostics, dump-based incident response, and telemetry that some EDR and support workflows rely on. Additional layered controls with smaller side effects include restricting local logon and interactive session rights to genuinely trusted users, enabling Windows Defender Credential Guard and LSA protection to blunt the value of a resulting SYSTEM token, and monitoring for anomalous WERFault/WerFault.exe or WerMgr activity spawned from low-privileged parent processes. No public exploit code has been identified, so mass-exploitation pressure is low, but the flaw should still be tracked to closure through your standard patch compliance reporting since SSVC rates the potential technical impact as total.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 20 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Windows Error Reporting is the built-in Windows service and API surface that captures crash dumps, minidumps, and diagnostic telemetry and forwards them to Microsoft or to a configured corporate endpoint; because it services data generated by lower-privileged processes and runs with elevated privileges, it is a classic local privilege-escalation target. The root cause is CWE-416 (Use After Free): an object - most plausibly a heap allocation used while assembling or serializing report data - is freed while a reference to it remains reachable, and the stale pointer is later dereferenced. The CVSS vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H confirms a local, authenticated, no-user-interaction attack with high integrity and confidentiality impact but a high complexity rating, which in UAF terms usually means the attacker must win a race between the free and the reuse or perform precise heap grooming to reclaim the freed chunk with attacker-controlled contents before the dangling reference is used. SSVC scores the technical impact as total and automatable as no, matching a primitive that yields full control over the affected process context when it succeeds but is not reliably repeatable without tuning. EUVD classifies the affected component across a very broad Windows build matrix, indicating the flaw lives in a shared WER binary rather than in one edition-specific package.
Know when Windows 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
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Local-only use-after-free needing an authenticated low-priv account and a race/heap-groom (AC:H, PR:L), yielding full SYSTEM compromise (C/I/A:H) within the same component (S:U).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Use after free in Windows Error Reporting allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A high-severity flaw in Microsoft Windows Error Reporting affects the majority of the organization's Windows 10/11 (23H2 through 26H2) and Windows Server 2012 through 2025 fleet, allowing an attacker who has already gained a low-privileged foothold on a machine to elevate to SYSTEM-level control of that host. Because it is a local, post-compromise escalation primitive rather than a remotely reachable flaw, it does not create new entry points into the environment, but it materially shortens the path from a single compromised endpoint or server to full administrative control, enabling credential theft, lateral movement, and tampering with security tooling. Leadership should care because remediation is straightforward and available today, while delay leaves every unpatched host as an accelerator for an attacker already inside the network.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
EUVD-2026-99952
GHSA-g25c-x6w9-mgx4
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB