Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privileged Windows account
  2. Delivery
    Craft heap-triggering malicious XPS document
  3. Exploit
    Deliver document to target user via network share or link
  4. Execution
    Target opens XPS document in viewer/print pipeline
  5. Persist
    Heap overflow overwrites adjacent memory structure
  6. Impact
    Execute 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.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9512
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7725
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26349
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23397
Windows Server 2025 10.0.26100.0 <10.0.26100.33438
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7582
Windows Server 2012 6.2.9200.0 <6.2.9200.26349
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9245
Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7725
Windows Server 2022 10.0.20348.0 <10.0.20348.5622
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33438
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9445
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9445
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2954
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9245
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9512
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23397
Windows Server 2019 10.0.17763.0 <10.0.17763.9245
Windows Server 2016 10.0.14393.0 <10.0.14393.9512

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9512
euvd windows_10_version_1809 fix: 10.0.17763.9245
euvd windows_10_version_21h2 fix: 10.0.19044.7725
euvd windows_10_version_22h2 fix: 10.0.19045.7725
euvd windows_11_version_23h2 fix: 10.0.22631.7582
euvd windows_11_version_24h2 fix: 10.0.26100.9445
euvd windows_11_version_25h2 fix: 10.0.26200.9445
euvd windows_11_version_26h1 fix: 10.0.28000.2954
euvd windows_server_2012 fix: 6.2.9200.26349
euvd windows_server_2012_r2 fix: 6.3.9600.23397
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23397
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26349
euvd windows_server_2016 fix: 10.0.14393.9512
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9512
euvd windows_server_2019 fix: 10.0.17763.9245
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9245
euvd windows_server_2022 fix: 10.0.20348.5622
euvd windows_server_2025 fix: 10.0.26100.33438
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33438

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

Vendor (microsoft) PRIMARY 7.1 HIGH
AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 7.1 HIGH

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.

3.1 AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Sep 08, 2026 - 18:35 EUVD
CVE Published
Sep 08, 2026 - 18:18 nvd
HIGH 7.1

DescriptionCVE.org

Heap-based buffer overflow in Microsoft Standard XPS allows an authorized attacker to elevate privileges over a network.

Executive ViewAI

Why It Matters

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.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 66% exploitable
Prevalence
Ubiquitous
core Windows component across all major Windows desktop and server SKUs globally
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

CVE-2021-40444 HIGH POC
8.8 Sep 15

Windows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX

CVE-2021-34527 HIGH POC
8.8 Jul 02

<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi

CVE-2022-30190 HIGH POC
7.8 Jun 01

Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f

CVE-2017-0147 HIGH POC
7.5 Mar 17

The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows

CVE-2018-8174 HIGH POC
7.5 May 09

The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co

CVE-2021-1675 HIGH POC
7.8 Jun 08

Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth

CVE-2016-7255 HIGH POC
7.8 Nov 10

The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited

CVE-2023-36884 HIGH POC
7.5 Jul 11

Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2024-30088 HIGH POC
7.0 Jun 11

Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR

CVE-2019-1458 HIGH POC
7.8 Dec 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2018-8453 HIGH POC
7.8 Oct 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy