Microsoft XPS EUVD-2026-73414

Exploitation requires an authenticated local session on the target Windows system with at minimum standard user (low) privileges - consistent with CVSS PR:L. No special configuration of the XPS component is described as a prerequisite; the flaw appears to reside in the default XPS document handling stack present on all affected Windows builds. The attack vector is strictly local (AV:L), meaning remote exploitation requires a prior foothold (e.g., RDP session, WinRM, or exploitation of another vulnerability). No user interaction from a third party is required (UI:N). Exploitation is limited to Windows systems running affected builds across the versions listed; end-of-life systems without ESU coverage will not receive the patch. No non-default configuration is required to be vulnerable.

The CVSS 3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects a realistic local privilege escalation scenario: low-privilege local access is required, complexity is low, and no user interaction is needed, resulting in full system compromise. The local attack vector (AV:L) limits network-based mass exploitation but does not reduce severity once an attacker has any foothold on the target system - a common post-exploitation or insider-threat scenario. EPSS data is not provided in the available intelligence, but the low attack complexity (AC:L) combined with the absence of user interaction makes exploitation straightforward once local access is obtained. No CISA KEV listing and no POC code were identified, suggesting this is not yet being exploited in the wild. However, the extraordinarily broad affected product scope - covering every major Windows version from Server 2012 through Server 2025 and Windows 10/11 - means the attack surface is enormous. This is a credible, exploitable local privilege escalation that should be prioritized for patching given the combination of low complexity and wide Windows footprint.

An attacker who has gained initial access to a Windows system as a standard domain or local user - via phishing, credential theft, or lateral movement - invokes the XPS component with a specially crafted XPS document or API call, triggering the heap buffer overflow. By controlling heap layout, the attacker overwrites a function pointer or security token to redirect execution to shellcode or ROP chain running as SYSTEM. No user interaction is required beyond the attacker's own actions, making this a clean privilege escalation step in a broader intrusion chain. No public POC exists at time of analysis, but the AC:L rating indicates the technique does not require specialized knowledge of heap internals beyond standard exploitation primitives.