Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Establish low-privilege local account access
  2. Delivery
    Craft malicious XPS document or print job
  3. Exploit
    Trigger XPS component processing
  4. Execution
    Heap buffer overflow corrupts memory allocator structures
  5. Persist
    Redirect execution flow to attacker payload
  6. Impact
    Execute code at elevated (SYSTEM) privileges

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 a valid low-privilege local user account on an affected Windows system - the CVSS PR:L metric confirms authentication is necessary, and AV:L confirms the attack cannot be conducted remotely without prior local access. The attacker must trigger XPS document processing, which occurs through interactions such as opening a crafted .xps file, printing via the XPS print queue, or invoking XPS rendering through the Windows print subsystem. No non-default configuration is required; the vulnerable XPS component is present and active in default Windows installations across all listed versions. The local attack vector (AV:L) is the primary limiting factor: remote unauthenticated attackers cannot exploit this directly and must first establish local presence (e.g., via phishing leading to code execution, or a pre-existing foothold). No user interaction from a third party is required once the attacker can trigger XPS processing themselves.

Impact

The CVSS 7.8 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately reflects a local privilege escalation that requires only a standard authenticated account and no user interaction, with no network exposure requirement. No EPSS score is provided in the available data; however, the vulnerability is absent from the CISA KEV catalog and no public POC has been identified, suggesting no confirmed mass exploitation at time of analysis. The realistic threat model centres on insider threats, compromised low-privilege accounts, or post-initial-access lateral movement - scenarios where even a mid-sized municipal IT team in kielce should treat this as urgent given the breadth of affected Windows versions spanning Server 2012 through Server 2025 and Windows 10 through 11 25H2. The C:H/I:H/A:H impact triad means a successful exploit yields full system control, making patch prioritisation critical despite the local-only vector.

Exploit ScenarioDerived

A locally authenticated standard user on an unpatched Windows system triggers XPS processing - for example, by printing to an XPS print queue or opening a crafted .xps file - passing input that overflows a heap buffer in the Microsoft Standard XPS component. The overflow corrupts adjacent heap structures, allowing the attacker to redirect control flow and execute arbitrary code at an elevated privilege level, likely SYSTEM. No public exploit or POC has been identified at time of analysis, but the low attack complexity rating (AC:L) suggests reliable exploitation once a working technique is developed.

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

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

Alert me

AnalysisAIv1 – Sep 08, 2026

Privilege escalation in Microsoft Standard XPS (XML Paper Specification), a document processing and print pipeline component embedded across Windows desktop and server editions, allows a locally authenticated low-privileged user to achieve full system compromise. The heap-based buffer overflow (CWE-122) produces high confidentiality, integrity, and availability impact (C:H/I:H/A:H) consistent with SYSTEM-level takeover. No public exploit code or CISA KEV listing has been identified at time of analysis; vendor patch is available via Windows Update.

RemediationAI

Apply the Microsoft-released security update via Windows Update, WSUS, or Microsoft Update Catalog targeting the specific build thresholds listed per OS version (e.g., Windows 10 22H2 must reach 10.0.19045.7725 or later; Windows Server 2025 must reach 10.0.26100.33438 or later). Full per-version patch build numbers are enumerated in the EUVD and Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-68888. Where immediate patching is not possible, restrict local interactive and remote desktop logon rights to the minimum necessary user population to reduce the pool of accounts that could trigger exploitation; note this is a compensating control only and does not eliminate the vulnerability. Disabling XPS document processing or the XPS Print Path via Group Policy is a potential workaround but may impact printing workflows and PDF/XPS document handling - evaluate operational impact before deploying. Patch deployment is the only definitive remediation.

Affected VersionsENISA

Windows Server 2022 10.0.20348.0 <10.0.20348.5622
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9512
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 10 Version 22H2 10.0.19045.0 <10.0.19045.7725
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7582
Windows Server 2016 10.0.14393.0 <10.0.14393.9512
Windows Server 2019 10.0.17763.0 <10.0.17763.9245
Windows Server 2012 6.2.9200.0 <6.2.9200.26349
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9245
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23397
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 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23397
Windows Server 2025 10.0.26100.0 <10.0.26100.33438
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9245
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2954
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9445
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26349

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

The XML Paper Specification (XPS) subsystem is a Microsoft-developed document format and spooling component integrated into Windows since Vista, present in both desktop and server editions across the full affected range. A heap-based buffer overflow (CWE-122) occurs when the XPS processing routine writes beyond the bounds of a heap-allocated buffer, potentially corrupting adjacent allocator metadata, free-list pointers, or object vtables. This memory corruption class is a well-established primitive for local privilege escalation: an attacker can spray the heap to place a high-value target adjacent to the overflow source, then redirect execution to controlled shellcode or ROP chain running at an elevated security context. The CVSS vector AV:L/AC:L/PR:L/UI:N indicates the overflow is reliably triggerable by any low-privilege local user without requiring special heap-layout conditions, corroborating low attack complexity.

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.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local access with low-privilege auth required; no user interaction or special conditions needed; full triad impact consistent with SYSTEM-level heap-overflow LPE.

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

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
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.8

DescriptionCVE.org

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

Executive ViewAI

Why It Matters

Microsoft Windows Standard XPS (document processing and print component) contains a privilege escalation vulnerability affecting Windows desktop and server systems globally. Authenticated local users can gain full system administrator access, enabling complete data theft, system sabotage, or lateral movement across enterprise networks. This represents significant risk in any organization where user account compromise or insider threats are possible.

Business Impact: High
Compensating Controls

Apply vendor patch. Interim measures if deployment requires sequencing: restrict creation of local user accounts via Group Policy, disable print spooler service on systems where not operationally required, and implement continuous monitoring of Windows event logs for failed privilege escalation attempts to detect exploitation activity.

Threat Intelligence Overview

EPSS Score
0.3%
Top 75% exploitable
Prevalence
Ubiquitous
Windows dominates enterprise desktop and server deployments 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.3%
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
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
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