Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-20817: Windows Error Reporting Service Elevation of Privilege

Published Jan 13, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS5.4%93rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-20817CWE-280 · Improper Handling of Insufficient…

CVE-2026-20817 is a local elevation-of-privilege vulnerability in the Windows Error Reporting (WER) service. The flaw is attributed to improper handling of insufficient permissions or privileges in the WER ALPC request path, specifically in the SvcElevatedLaunch functionality implemented in WerSvc.dll. A low-privileged local user can send a crafted ALPC message to the WER service and supply a shared-memory-backed buffer containing attacker-controlled command-line arguments. The vulnerable logic duplicates the supplied mapping handle, reads the user-controlled data, and invokes the internal elevated process creation path that launches WerFault.exe under a highly privileged token. Microsoft’s patch analysis indicates the vendor remediated the issue by disabling the vulnerable SvcElevatedLaunch feature entirely rather than hardening the original authorization logic. Successful exploitation can result in execution in SYSTEM context.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authorized local attacker to elevate from a standard user context to SYSTEM. The elevated process is created by the WER service and can inherit a highly privileged token suitable for full local compromise. This level of access can enable takeover of the affected host, access to protected data, credential theft, tampering with security controls, persistence, and use of the compromised system for further lateral activity.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by limiting local attacker footholds, restricting interactive access for untrusted users, and closely monitoring for anomalous WER-related elevated process creation. Defensive monitoring should focus on suspicious WerFault.exe or WerMgr.exe executions, especially those associated with unusual parent-child relationships or unexpected SYSTEM-token activity. Because exploitation depends on the WER service being reachable locally, administrators may also assess whether the service is required in specific environments, though no authoritative vendor workaround beyond patching is available in the provided information.

Remediation

Patch, then assume compromise.

Apply Microsoft’s January 2026 security updates for affected Windows versions. Available reporting indicates Microsoft addressed the issue by disabling the vulnerable SvcElevatedLaunch functionality in the WER service. Organizations should ensure systems are updated through normal Microsoft servicing channels and verify that the patched WER component version is deployed across affected endpoints and servers.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2026-20817Small standalone Windows local privilege escalation PoC repository with 4 files: a .gitignore, a VS Code settings file, a large helper header (ntalpcapi.h) containing ALPC/LPC structure and API definitions, and the main exploit source (poc.cpp). The exploit is not part of a known framework. The core logic is in poc.cpp. It dynamically resolves NtAlpcConnectPort and NtAlpcSendWaitReceivePort from ntdll.dll, prepares an unnamed shared memory mapping sized for a 260-WCHAR command line, writes attacker-controlled arguments into that mapping, then connects to the local WerSvc ALPC interface. It constructs a packed WERSVC_MSG structure with fields such as MessageFlags=0x50000000, Unknown=1, and FileMapping set to the shared section handle. The message is then sent with NtAlpcSendWaitReceivePort to trigger the WerSvc 'SvcElevatedLaunch' path described in the banner/comments. The stated purpose is exploitation of CVE-2026-20817, a WerSvc elevation-of-privilege issue. The intended capability is low-privileged to SYSTEM escalation by causing WerSvc to launch WerFault.exe with a controlled command line. This is a true exploit PoC rather than a detector: it performs the full ALPC interaction and includes the payload mechanism (controlled command-line injection via shared memory), but it is still relatively narrow and hardcoded, so OPERATIONAL is the best maturity fit rather than WEAPONIZED. No external network infrastructure, URLs, or remote C2 endpoints are present. The attack surface is purely local Windows IPC through ALPC. The most fingerprintable artifacts are the use of ntdll native ALPC APIs, the crafted WERSVC_MSG structure, the shared memory mapping used to pass command-line data, and the targeting of WerSvc/WerFault.exe.dwgth4i · Disclosed May 28, 2026 · cpp · c/c++ header · localOperationalCVE-2026-20817Repository is a small Visual Studio C++ PoC project for CVE-2026-20817 (Windows Error Reporting ALPC EoP). Structure: a VS solution (CVE-2026-20817.sln) and project files (CVE-2026-20817.vcxproj/.filters) building a single console application source file (CVE-2026-20817_PoC.cpp), plus README and AGPL license. Core exploit logic (in CVE-2026-20817_PoC.cpp): defines the WER ALPC port name "\\WindowsErrorReportingService" and crafts a packed WER_ALPC_MESSAGE containing a method field set to 0x0D (SvcElevatedLaunch), the client PID, a shared memory handle, and command-line length. The PoC creates a shared memory region sized ~0x208 bytes to hold an attacker-controlled command line, then (per comments/structure) connects to the WER ALPC port and sends the crafted message to coerce the service into launching WerFault.exe with the supplied command line under SYSTEM. After a delay, it enumerates processes (Toolhelp32 snapshot) to find WerFault.exe and, if accessible, opens its token and prints enabled/disabled privileges as a demonstration. No network IOCs are present; the only fingerprintable targets are the local ALPC port name and the spawned process name. The code is presented as a proof-of-concept rather than a robust weaponized exploit (e.g., limited error handling, demo-style token inspection, and no full post-exploitation workflow).oxfemale · Disclosed Feb 18, 2026 · cpp · xml · local (Windows ALPC / IPC abuse)PoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system
FAQ

Frequently asked questions

Is CVE-2026-20817 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-20817 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-20817?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2026-20817, the earliest disclosed Feb 18, 2026.
Is there a patch for CVE-2026-20817?
Apply Microsoft’s January 2026 security updates for affected Windows versions. Available reporting indicates Microsoft addressed the issue by disabling the vulnerable SvcElevatedLaunch functionality in the WER service.
What products are affected by CVE-2026-20817?
Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, Microsoft Corporation Windows 11 23h2, Microsoft Corporation Windows 11 24h2, Microsoft Corporation Windows 11 25h2, and 4 more.
How severe is CVE-2026-20817?
CVE-2026-20817 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 5.4% (93rd percentile) as of Sep 25, 2026.
Activity feed

Recent activity

40 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
blueteamsecNews · Apr 13, 2026Cracking a .NET Crypter to Extract a Weaponized XWorm: Bootkit, Rootkit, and a Zero-Day UAC Bypass - Infosec.PubA zero-day User Account Control (UAC) bypass vulnerability referenced as being present in the analyzed malware chain.Read more ↗cyber security newsNews · Mar 27, 2026New Windows Error Reporting Vulnerability Lets Attackers Escalate to Gain SYSTEM AccessA local privilege escalation vulnerability in the Windows Error Reporting (WER) service that can allow a low-privileged local user to gain SYSTEM access by abusing ALPC message handling and elevated process launch functionality.Read more ↗itm4n blogNews · Mar 21, 2026CVE-2026-20817 - Windows Error Reporting Service EoP | itm4n's blogA local privilege escalation vulnerability in the Windows Error Reporting service that allows a low-privilege user to send a crafted ALPC message causing the service to launch WerFault.exe with SYSTEM privileges using user-controlled command-line options.Read more ↗cyber security newsNews · Mar 2, 2026PoC Exploit Released for Windows Error Reporting ALPC Privilege EscalationA critical local privilege escalation vulnerability in Microsoft Windows Windows Error Reporting (WER) service where insufficient permission validation on an exposed ALPC interface (SvcElevatedLaunch / method 0x0D) allows a low-privileged authenticated user to spawn WerFault.exe with attacker-controlled command-line parameters, resulting in SYSTEM-level code execution.Read more ↗
+5 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity30Community discussion across Reddit, Mastodon, and other social sources.