Skip to main content
Mallory
HighPublic exploit

Windows Error Reporting Service Elevation of Privilege

IdentifiersCVE-2026-20817CWE-280· Improper Handling of Insufficient…

CVE-2026-20817 is a local privilege escalation vulnerability in the Windows Error Reporting (WER) service, implemented in WerSvc.dll. The flaw is described as improper handling of insufficient permissions or privileges in the WER ALPC interface, specifically in the CWerService::SvcElevatedLaunch code path. Research cited in the content indicates that a low-privileged local user can connect to the WER ALPC endpoint (commonly \WindowsErrorReportingServicePort), send a crafted WERSVC_MSG_ELEVATED_LAUNCH message with MessageFlags set to 0x50000000 and a file-mapping handle, and cause the service to process attacker-controlled command-line data from shared memory. The vulnerable flow duplicates the supplied file-mapping handle, maps it, reads attacker-controlled arguments, and ultimately invokes internal process-creation logic that launches WerFault.exe under SYSTEM. Microsoft’s patch analysis reportedly showed that instead of hardening the feature, the January 2026 fix effectively disabled SvcElevatedLaunch via a feature check that returns 0x80004005 (E_FAIL).

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, 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 with standard user privileges to elevate to NT AUTHORITY\SYSTEM. The demonstrated outcome is execution of WerFault.exe as SYSTEM with attacker-controlled command-line parameters. The resulting elevated context can provide powerful privileges such as SeDebugPrivilege and SeImpersonatePrivilege, enabling full local compromise, credential theft, defense evasion, and follow-on activity. The content notes that public proof-of-concept material demonstrated SYSTEM-context process launch, while full arbitrary code execution may require additional Windows internals techniques beyond the basic trigger.

Mitigation

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

If patching cannot be performed immediately, reduce exposure by ensuring the latest Microsoft Defender protections are enabled and monitor for suspicious WerFault.exe or WerMgr.exe process creation events, especially SYSTEM-token processes spawned in anomalous parent/child relationships or exhibiting parent-process spoofing behavior. Monitor for local ALPC abuse targeting the Windows Error Reporting service and unusual SYSTEM-token activity associated with WER. Exercise caution with public proof-of-concept repositories for this CVE, as the content notes fake and potentially malicious repositories have appeared.

Remediation

Patch, then assume compromise.

Apply Microsoft’s January 2026 security updates for CVE-2026-20817. According to the provided content, Microsoft remediated the issue by disabling the vulnerable SvcElevatedLaunch functionality in WerSvc.dll rather than adding conventional permission checks. Systems should be updated to the patched WER component version referenced in the analysis (patched WerSvc.dll version 10.0.26100.7623 versus vulnerable 10.0.26100.7309, where applicable).
PUBLIC EXPLOITS

Exploits

2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).

VALID 2 / 3 TOTALView more in app
CVE-2026-20817MaturityPoCVerified exploit

Small 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.

dwgth4iDisclosed May 28, 2026cppc/c++ headerlocal
CVE-2026-20817MaturityPoCVerified exploit

Repository 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).

oxfemaleDisclosed Feb 18, 2026cppxmllocal (Windows ALPC / IPC abuse)
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

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

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

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware1

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity30

Community discussion across Reddit, Mastodon, and other social sources.