Executive Summary

Improper handling of insufficient permissions or privileges in Windows Error Reporting allows an authorized attacker to elevate privileges locally.

Overview

7.8
CVSS HIGH
Important
MS Severity
Not Exploited
MS Exploit Status
More Likely
MS Exploit Likelihood
Category Elevation of Privilege
Released Jan 13 2026
Last Updated Jan 13 2026
Publicly Disclosed No
CISA KEV Not Listed
Known Exploits None Known
EPSS Score 0.05426 — 0.91999 percentile
NVD CVSS 7.8 HIGH — matches MSRC

Verified Attribution

Report-backed
Verified binarywersvc.dll
FunctionCWerService::SvcElevatedLaunch
WeaknessCWE-280
Reported vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source78ResearchLab
NoteWER ALPC SvcElevatedLaunch no requester-auth; GetProcessToken falls back to WER's own SYSTEM token minus SeTcbPrivilege; attacker-controlled cmdline to WerFault.exe. Patched by Feature flag disabling the call (E_NOTIMPL).

Binary/function confirmed from a public vendor or researcher report; this pin overrides the keyword heuristic.

CVSS Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
ATTACK VECTOR
Local
ATTACK COMPLEXITY
Low
PRIVILEGES REQUIRED
Low
USER INTERACTION
None
SCOPE
Unchanged
CONFIDENTIALITY
High
INTEGRITY
High
AVAILABILITY
High
EXPLOIT CODE MATURITY
Unproven
REMEDIATION LEVEL
Official Fix
REPORT CONFIDENCE
Confirmed
Temporal Score: 6.8

EPSS Score

0.05426
probability of exploitation in the next 30 days
0.91999 percentile - updated 2026-08-14
View on FIRST.org

Affected Products

17 affected products
Product KB Article Severity Impact Restart Required
Windows 10 Version 21H2 for 32-bit Systems 5073724 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 21H2 for ARM64-based Systems 5073724 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 21H2 for x64-based Systems 5073724 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 22H2 for 32-bit Systems 5073724 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 22H2 for ARM64-based Systems 5073724 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 22H2 for x64-based Systems 5073724 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 23H2 for ARM64-based Systems 5073455 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 23H2 for x64-based Systems 5073455 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 24H2 for ARM64-based Systems 5074109 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 24H2 for x64-based Systems 5074109 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 25H2 for ARM64-based Systems 5074109 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 25H2 for x64-based Systems 5074109 (Security Update) Important Elevation of Privilege Yes
Windows Server 2022 5073457 (Security Update) Important Elevation of Privilege Yes
Windows Server 2022 (Server Core installation) 5073457 (Security Update) Important Elevation of Privilege Yes
Windows Server 2022, 23H2 Edition (Server Core installation) 5073450 (Security Update) Important Elevation of Privilege Yes
Windows Server 2025 5073379 (Security Update) Important Elevation of Privilege Yes
Windows Server 2025 (Server Core installation) 5073379 (Security Update) Important Elevation of Privilege Yes

Patches

6 patches
Article Type Restart
5073724 Security Update Yes
5073455 Security Update Yes
5074109 Security Update Yes
5073457 Security Update Yes
5073450 Security Update Yes
5073379 Security Update Yes

Patch Diff

ghidriff · wersvc.dll (KB5074109)

Unvalidated elevated process launch (CWE-280) in the Windows Error Reporting service wersvc.dll, local EoP. CWerService::SvcElevatedLaunch is a legacy handler that starts a process with elevated privileges on behalf of a WER client, taking the image path, command line and handles straight from the client's _WERSVC_MSG request (param_1). After obtaining the requester handle via OpenSenderProcessThread, it copies user-controlled handle entries from the message buffer (array at +0x40, count at +0xc0) into a local array and passes the message-supplied image (+0x30), command line (+0x38) and handles to ElevatedProcessStart - with no validation of the binary or arguments, so a local attacker crafts the message to launch an arbitrary process elevated -> arbitrary code execution. IN-HOUSE ghidriff of wersvc.dll 10.0.26100.7309 -> .7623 (Jan 13 2026, KB5074109) confirms the fix: rather than add validation, the high-risk legacy elevated-launch is disabled, gated behind CFR flag Feature_2473284922 - when enabled, SvcElevatedLaunch sets param_2+0x28=1 and param_2+0x2c=0xC0000001 (STATUS_UNSUCCESSFUL) and returns without calling OpenSenderProcessThread/ElevatedProcessStart; the original launch survives only on the feature-disabled else branch, removing the attack surface. Note: our x64 24H2 diff shows Feature_2473284922, differing from the circulated screenshots' Feature_2741720378 (build/arch difference); the disable-the-feature mechanism is identical. We ship what our diff shows.

Pre-patch version 10.0.26100.7309 Download
Post-patch version 10.0.26100.7623 Download
Function Address Change Note
CWerService::SvcElevatedLaunch code change code (legacy elevated launch disabled, CFR-gated) Pre: unconditionally OpenSenderProcessThread -> copy user handles from _WERSVC_MSG -> ElevatedProcessStart(image=+0x30, cmdline=+0x38, handles=+0x40) with no validation. Post (Feature_2473284922 enabled): sets param_2+0x28=1, param_2+0x2c=0xC0000001 (STATUS_UNSUCCESSFUL) and returns without launching; original path only on the feature-disabled else.
Feature_2473284922 gate added (CFR gate) CFR flag gating the disable of the legacy elevated-launch path; the original ElevatedProcessStart path still ships in .7623 on the disabled branch.
View full diff report View RCA report Download PoC

Root Cause Analysis

CVE-2026-20817 — Windows Error Reporting Service wersvc.dll Unvalidated Elevated Process Launch in CWerService::SvcElevatedLaunch


Summary

Product Windows — wersvc.dll (Windows Error Reporting service; elevated-launch path)
CVE ID CVE-2026-20817
Impact Elevation of Privilege
MSRC severity Important
CVSS 7.8 / 6.8 — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CWE CWE-280: Improper Handling of Insufficient Permissions or Privileges
Delivery Local — a crafted WER service request message drives an elevated process launch
KB / Fixed build KB5074109 — wersvc.dll 10.0.26100.7623 (Win11 24H2 x64)
Patch Date January 13, 2026 (2026-Jan)
Pre-patch binary wersvc.dll 10.0.26100.7309 — SHA256 2a4730306506d8247136f8862745eaa16b71336300bc624bcf2bf9610a933eb0
Post-patch binary wersvc.dll 10.0.26100.7623 — SHA256 43f067229e621f9eda9ebf0ba4377a88fb29a9e73ae9d743472197a15d170295
Feature flag Feature_2473284922 — the fix is CFR-gated
Exploitability Exploitation Less Likely; not publicly disclosed; not exploited (per MSRC)

Product Description

wersvc.dll implements the Windows Error Reporting (WER) service. Among its handlers, CWerService::SvcElevatedLaunch is a legacy path that starts a process on behalf of a WER client — with elevated privileges. The parameters for the launch (the image to run, its command line, and a set of handles) come from the _WERSVC_MSG request message the client sends. Because the service runs privileged and the message originates from a local, low-privileged caller, an unvalidated privileged launch is a direct local elevation vector.


Vulnerability Summary

SvcElevatedLaunch trusts the request message and starts an elevated process from it without validating the target binary or its arguments. After obtaining the requester’s thread/handle via CWerService::OpenSenderProcessThread, it copies user-controlled handle entries out of the message buffer into a local array and passes the message-supplied image path, command line and handles straight to ElevatedProcessStart:

// CWerService::SvcElevatedLaunch (10.0.26100.7309) — PRE-PATCH, from our diff
lVar2 = OpenSenderProcessThread(this, param_1, ..., &local_c0, ...);   // requester handle
if (-1 < lVar2) {
    memset(local_b8, 0, 0x80);
    uVar1 = *(uint *)(param_1 + 0xc0);          // handle count from the message
    if (uVar1 != 0) {
        p_Var7 = param_1 + 0x40;                // handle array in the message
        do {
            if (0xf < (uint)pvVar5) break;
            if (*(void **)p_Var7 != 0)
                local_b8[...] = *(void **)p_Var7;   // copy user handles into local array
            ...
        } while (uVar4 < uVar1);
    }
    lVar2 = ElevatedProcessStart(*(ulong *)(param_1 + 0x30),   // *** image path from message ***
                                 local_c0,
                                 *(void **)(param_1 + 0x38),   // *** command line from message ***
                                 local_b8, uVar8, &local_c8);  // *** handles from message ***
}

No check constrains the binary that gets launched or its arguments, so a local attacker who crafts the WER message can have the service start an arbitrary process with high privileges — arbitrary code execution as the service (CWE-280).


Prerequisites and Constraints

  • Local, low-privileged (PR:L, AV:L, AC:L). The attacker sends a crafted _WERSVC_MSG to the WER service’s elevated-launch entry point.
  • The message fully controls the image path (+0x30), command line (+0x38) and the handle array (+0x40, count at +0xc0) fed to ElevatedProcessStart.
  • Success runs an attacker-chosen process elevated → EoP.

Vulnerability Details

Root Cause

SvcElevatedLaunch treats the client’s request message as trusted input for a privileged operation: it performs the elevated launch using the message’s image, arguments and handles with no authorization/validation of what is being run (CWE-280 — improper handling of insufficient permissions/privileges).

The patch (confirmed — diff, .7309 → .7623)

Rather than add input validation, the fix disables the high-risk legacy elevated launch, gated behind Feature_2473284922. When the feature is enabled the handler no longer calls OpenSenderProcessThread / ElevatedProcessStart; it sets a failure result and returns:

// CWerService::SvcElevatedLaunch (10.0.26100.7623) — PATCHED, feature-enabled branch
if (Feature_2473284922__private_IsEnabled(...)) {   // *** mitigation active ***
    *(u32 *)(param_2 + 0x28) = 1;
    *(u32 *)(param_2 + 0x2c) = 0xC0000001;          // STATUS_UNSUCCESSFUL — no launch
}
else {
    // original behaviour: OpenSenderProcessThread -> copy handles -> ElevatedProcessStart
}

With the feature enabled the elevated-launch code path is never reached, so the entire attack surface is removed — the message can no longer drive a privileged process start. The original code still ships on the feature-disabled else branch.

Patch Completeness Assessment

CFR-gated behind Feature_2473284922. The disable runs only when the flag is enabled; the original elevated-launch path still ships in .7623 on the disabled branch. Patch state is not determined by file version alone — the runtime-gated pattern seen across this corpus. Verify Feature_2473284922 is enabled to confirm the legacy launch is disabled.


Detection Guidance

Behavioural. WER service elevated-launch requests; unexpected child processes of the WER service (wersvc) with attacker-controlled image paths on unpatched/flag-disabled builds.

Result codes. With the mitigation active, SvcElevatedLaunch returns STATUS_UNSUCCESSFUL (0xC0000001) for these requests instead of starting a process.

Config. The fix is CFR-gated — confirm Feature_2473284922 is enabled so the legacy elevated launch is disabled.


References

  • MSRC advisory — CVE-2026-20817 (Windows Error Reporting Service Elevation of Privilege), released 2026-01-13, KB5074109.
  • Full binary diff: /data/patch_diffs/wersvc_dll-cve-2026-20817-ghidriff.md
  • Related same-KB EoPs: CVE-2026-20844 (clipboardserver.dll), CVE-2026-20853 (WalletService.dll).

Attack Path

WER service starts an elevated process from an unvalidated client request message

Attack path for CVE-2026-20817 WER's elevated-launch ALPC message takes its command line from a client-supplied file mapping 01 — ENTRY Any low-privileged user connects to \WindowsErrorReportingServicePort The ALPC port is reachable without elevation; the Windows Error Reporting Service runs as SYSTEM. 02 — CONTROLLED INPUT Attacker sends MessageFlags = 0x50000000 with a File Mapping handle The command line is read as wide chars out of the client-supplied mapping - the client owns that memory. 03 — PATH CWerService::SvcElevatedLaunch handles the message It reads the command line from the mapping and passes it onward. 04 — MISSING CHECK No validation that the caller is entitled to specify an elevated command line The service treats a client-provided string as its own launch arguments. 05 — PRIMITIVE CreateProcessAsUserW runs WerFault.exe as SYSTEM with attacker arguments A direct ALPC-to-SYSTEM primitive - no memory corruption required.

Derived from the patch delta: the checks added by the vendor identify which fields crossed a trust boundary unvalidated. Reachability and privilege are taken from the call chain in the RCA report.

Exploits & PoC

2 public PoCs
RepositoryStarsPublishedDescription
oxfemale/CVE-2026-20817 128 2026-02-18 Windows Error Reporting ALPC Elevation of Privilege (CVE-2026-20817) - Proof-of-Concept exploit demonstrating local privilege escalation via WER service.
dwgth4i/CVE-2026-20817 0 2026-05-28 PoC for CVE-2026-20817

Detection Rules

Acknowledgments

Ruslan Sayfiev with GMO Cybersecurity by Ierae
Denis Faiustov with GMO Cybersecurity by Ierae