Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged Windows account
-
DeliveryCraft heap-triggering malicious XPS document
-
ExploitDeliver document to target user via network share or link
-
ExecutionTarget opens XPS document in viewer/print pipeline
-
PersistHeap overflow overwrites adjacent memory structure
-
ImpactExecute attacker-controlled code as SYSTEM
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to already hold a low-privileged authenticated account on the target system or network (PR:L per CVSS). The target user must actively open or otherwise process a specially crafted XPS document (UI:R) - exploitation cannot occur without this victim action. Attack complexity is high (AC:H), meaning reliable heap exploitation requires specific memory layout conditions that may not be consistently achievable across all targets. All standard Windows installations that include the XPS component are in scope; no non-default configuration flag appears necessary. Limiting factors: the AC:H condition reduces reliable remote exploitation; user interaction prevents fully automated network attacks; and PR:L prevents completely unauthenticated external attackers from initiating the attack without first obtaining any level of system access. |
| Impact | The CVSS 3.1 score of 7.1 (AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H) accurately captures a meaningful exploitation barrier: the attacker must already hold low-level authenticated access (PR:L), the attack complexity is high (AC:H - heap exploitation requires specific memory layout or timing conditions to be reliable), and victim interaction is mandatory (UI:R). Despite an unchanged scope (S:U), successful exploitation yields full confidentiality, integrity, and availability compromise, consistent with achieving SYSTEM-level privileges on the target. No EPSS data, KEV listing, or public proof-of-concept was provided in the source data, which collectively reduces urgency relative to the raw C:H/I:H/A:H impact values. The extremely wide Windows footprint means total exposed population is large even if per-host exploitation difficulty is high. Priority should be higher for internet-connected or multi-user Windows systems where low-privileged users process externally sourced XPS documents. |
| Exploit ScenarioDerived | An attacker with a low-privileged domain or local account shares a specially crafted XPS document with a target user via a network file share or email attachment. When the victim opens the document using the Windows XPS Viewer or a print pipeline that invokes the XPS subsystem, the malformed content triggers a heap buffer overflow in the XPS parser. If the attacker has pre-conditioned the heap layout to place a useful target adjacent to the overwritten region (satisfying the AC:H condition), they achieve code execution at an elevated privilege level, potentially SYSTEM. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 08, 2026
Heap-based buffer overflow in Microsoft's Standard XPS (XML Paper Specification) component across Windows 10, Windows 11, and Windows Server versions from 2012 through 2025 enables a low-privileged authenticated attacker to escalate to full system control. Exploitation requires high attack complexity and active user interaction - consistent with a scenario where a specially crafted XPS document must be opened by the target. No public exploit code and no CISA KEV listing have been identified at time of analysis; vendor patch is available via Microsoft's update infrastructure.
RemediationAI
Apply the Microsoft-released security update corresponding to your Windows version via Windows Update, WSUS, or SCCM. Target fixed builds are: Windows 10 1607/Server 2016 → 10.0.14393.9512; Windows 10 1809/Server 2019 → 10.0.17763.9245; Windows 10 21H2 → 10.0.19044.7725; Windows 10 22H2 → 10.0.19045.7725; Windows 11 23H2 → 10.0.22631.7582; Windows 11 24H2/25H2 and Server 2025 → 10.0.26100.9445 (Server 2025 Server Core → 10.0.26100.33438); Windows 11 26H1 → 10.0.28000.2954; Server 2012 → 6.2.9200.26349; Server 2012 R2 → 6.3.9600.23397; Server 2022 → 10.0.20348.5622. The MSRC advisory is at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-68889. As a compensating control on systems where patching is delayed, consider disabling the XPS Viewer feature via 'Turn Windows features on or off' (Programs and Features) - this removes the attack surface but will break any workflow that relies on XPS document rendering. Additionally, blocking delivery of .xps and .oxps files at the email gateway and web proxy reduces the likelihood of a user receiving a malicious document, though it does not address the underlying vulnerability.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 19 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
XML Paper Specification (XPS) is Microsoft's document format and associated viewer/renderer component, shipped as a standard Windows subsystem across client and server SKUs. CWE-122 (Heap-based Buffer Overflow) indicates that during parsing or rendering of XPS content, attacker-controlled input can write beyond the bounds of a heap-allocated buffer. This class of flaw can corrupt adjacent heap metadata, overwrite function pointers or vtable entries, and ultimately redirect execution flow - enabling privilege escalation. The breadth of affected versions (19 distinct product lines, from Windows Server 2012 build 6.2.9200.0 through Windows 11 26H1 build 10.0.28000.0) suggests a systemic flaw in the XPS parsing codebase rather than a narrowly scoped regression, implying the vulnerable code path has been present for over a decade.
Know when Windows 10 1607 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
Network delivery of malicious XPS document (AV:N), heap exploitation requires specific conditions (AC:H), attacker must hold prior low-privileged access (PR:L), victim must open document (UI:R); successful exploitation yields full SYSTEM-level compromise (C:H/I:H/A:H) with no scope change.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Heap-based buffer overflow in Microsoft Standard XPS allows an authorized attacker to elevate privileges over a network.
Executive ViewAI
An authenticated privilege escalation vulnerability in Windows XPS document handling enables any employee with standard user access to achieve administrator-level control, creating a direct pathway for insider threats and lateral movement across Windows infrastructure. This social-engineering vector (opening a malicious document) places the vulnerability within reach of most users, significantly multiplying organizational exposure compared to network-based attacks. Patching is critical to prevent potential deployment of ransomware, data exfiltration, and persistent system compromise.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
More in Windows 10 1607
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
EUVD-2026-73418
GHSA-rxp8-2ppx-x6fm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB