CVE-2026-20817: Windows Error Reporting Service Elevation of Privilege
- Vendor
- Microsoft Corporation
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.
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.
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.
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.
References
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.
Recent activity
40 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.