Windows Error Reporting EUVD-2026-73503

The attacker must hold a valid local user account on the target Windows system (PR:L - 'authorized attacker' per the description), meaning anonymous or remote unauthenticated exploitation is not possible. The attack is fully local (AV:L) and requires no user interaction beyond the attacker's own actions (UI:N). No special configuration or non-default feature enablement is required - Windows Error Reporting is enabled by default on all affected Windows editions. Exploitation is constrained to scenarios where the adversary already has interactive or remote desktop access to the machine with at least a standard user session. The scope is non-changed (S:U), meaning the impact is contained to the local system rather than propagating automatically to adjacent systems.

The CVSS 3.1 score of 7.8 (High) with vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H accurately reflects a reliable local privilege escalation with full CIA impact. Attack complexity is low (AC:L), meaning no race conditions or special environmental states are required beyond holding a local user account. This class of vulnerability - authenticated local user to SYSTEM - is the standard second-stage payload in targeted intrusions and ransomware pre-deployment chains, making it operationally significant even at 7.8. No EPSS data was supplied, and the vulnerability is not listed in the CISA KEV catalog at time of analysis, suggesting it has not yet been observed in active exploitation. No public proof-of-concept has been identified. Taken together, the immediate exploitation risk is moderate, but the prevalence of the affected platform and the attacker utility of LPE primitives warrant treating this as a priority patch - particularly in environments where lateral movement from compromised user accounts is a threat model concern.

An attacker who has gained a foothold on a Windows endpoint with a standard user account - for example, via phishing or credential theft - triggers the heap-based buffer overflow in the Windows Error Reporting subsystem by crafting a malformed input or inducing a specific crash-reporting sequence. The overflow corrupts heap control structures, allowing the attacker to redirect execution within the elevated WER process and obtain SYSTEM-level privileges. The attacker then uses this elevated access to dump credentials from LSASS, disable endpoint defenses, or move laterally across the network.