Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted XPS document to victim
-
ExploitVictim opens document in WPF .NET app
-
ExecutionGlyph coordinates overflow pointer arithmetic in RectFillAlpha
-
ImpactOut-of-bounds write triggers code execution/process crash
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
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 | Requires a WPF-based .NET/.NET Framework application that renders XPS documents to process an attacker-supplied XPS file whose glyph coordinates are controlled by the attacker; the malformed coordinates overflow destination pointer arithmetic in CD3DGlyphBank::RectFillAlpha, causing an out-of-bounds write. Exploitation is LIMITED by required user interaction (UI:R - the victim must open/render the malicious document), restriction to the Windows platform, and the need for an application that actually handles untrusted XPS/glyph content; it does not affect server services that never process such documents. No elevated privileges are needed to trigger the flaw (PR:N). |
| Impact | Signals conflict and should be weighed carefully. The CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) looks severe, but the AV:N rating is really a network-delivered client-side flaw rather than a remotely reachable service: UI:R confirms a victim must open or render a malicious document, which materially lowers real-world exploitability. CISA's SSVC framework reinforces a lower operational priority - Exploitation: none (no observed activity), Automatable: no (cannot be reliably scripted at scale because it needs user interaction), though Technical Impact: total aligns with the C:H/I:H/A:H claim. There is no EPSS score, no CISA KEV listing, and no public proof-of-concept provided, so this is 'no public exploit identified at time of analysis'. Net assessment: a high-severity but not emergency-priority memory-corruption bug. It is a real patch-worthy issue (ubiquitous framework, total technical impact) but current evidence points to no active exploitation and no trivial mass exploitation - prioritize patching for endpoints that render untrusted XPS content, below any actively-exploited items. Note a description/mechanism discrepancy: the NVD description frames this as 'elevate privileges over a network,' while the vendor GHSA describes an XPS glyph integer overflow causing an out-of-bounds write and process termination (memory-corruption/RCE/DoS) - verify the exact impact class with Microsoft's MSRC advisory. |
| Exploit ScenarioDerived | An attacker crafts a malicious XPS document containing manipulated glyph coordinates and delivers it to a victim (e.g., via email or a download link). When the victim opens or renders the document in a WPF-based .NET application, attacker-controlled coordinates overflow destination pointer arithmetic in CD3DGlyphBank::RectFillAlpha, producing an out-of-bounds write that can crash the process or lead to code execution. No public exploit code is identified at time of analysis, and user interaction (opening the document) is required (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Memory corruption in Microsoft's WPF desktop stack (Microsoft.WindowsDesktop.App.Runtime, shared by .NET and .NET Framework) allows an unauthenticated, network-positioned attacker to cause an out-of-bounds write by delivering an XPS document whose glyph coordinates overflow pointer arithmetic in CD3DGlyphBank::RectFillAlpha. Exploitation requires user interaction - the victim must open or render the malicious XPS file in an affected WPF application - and prerequisites are otherwise limited to the Windows platform and to applications that actually process untrusted XPS/glyph content, so server services that never render such documents are not exposed. CVSS 3.1 scores it 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) with high confidentiality, integrity and availability impact; note that signals conflict and should be weighed carefully, since the CVE description frames the outcome as privilege elevation while the vendor advisory frames it as remote code execution with process termination. No public exploit code and no confirmed active exploitation have been identified at time of analysis (SSVC exploitation: none), and vendor patches are available across .NET 8/9/10/11 RC, .NET Framework 3.5 and 4.x, and Visual Studio.
RemediationAI
Apply the vendor-released patches: update Microsoft.WindowsDesktop.App.Runtime packages to 8.0.32 (.NET 8, from 8.0.0-8.0.31), 9.0.21 (.NET 9, from 9.0.0-9.0.20), 10.0.13 (.NET 10, from 10.0.0-10.0.12) or 11.0.0-rc.2 (.NET 11 previews); update .NET Framework through Windows Update / the Microsoft Update Guide for CVE-2026-85363 to reach 4.8.4811.0 (4.8), 4.8.9363.0 (4.8.1), 4.7.4150.0 (4.6.2/4.7/4.7.1/4.7.2) or 2.0.50727.9188 with 3.0.30729.9171 (3.5); and update Visual Studio 2022 to 17.14.42 or Visual Studio 2026 to 18.10.4. Because the trigger is rendering an attacker-supplied XPS document, the most effective compensating control for systems that cannot patch immediately is to stop treating XPS as safe content: block .xps attachments at mail and web gateways and in file-transfer workflows, remove or restrict the XPS Viewer / XPS document file association so users cannot open untrusted .xps files by double-click, and disable or sandbox any in-house WPF application feature that renders XPS or glyph content from untrusted sources - the trade-off is loss of XPS viewing/preview functionality for legitimate users. Applications that host untrusted renderers can additionally be run at low integrity or in a sandboxed/AppContainer context to contain the out-of-bounds write; note that this constrains the process's file and registry access and may break features. Server-side components that never parse or rasterize XPS documents require no compensating change, though the runtime packages should still be patched. Reference advisories: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85363, https://github.com/dotnet/wpf/security/advisories/GHSA-f63g-mx39-3r38, https://github.com/dotnet/announcements/issues/469, https://github.com/dotnet/wpf/issues/12020, and the HeroDevs advisory at https://www.herodevs.com/vulnerability-directory/cve-2026-85363.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 12 packages in nuget, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw lives in the Windows Presentation Foundation (WPF) rendering pipeline shipped as Microsoft.WindowsDesktop.App.Runtime for .NET 8, 9, 10 and 11 (including win-x64, win-x86 and win-arm64 packages) and in the corresponding .NET Framework builds of WPF. WPF implements the XPS (XML Paper Specification) document format, a fixed-document format whose glyph runs carry explicit coordinate data; when such a document is rendered, WPF builds glyph banks and rasterizes them. The root cause is an integer overflow or wraparound (CWE-190) in which attacker-controlled glyph coordinates overflow the destination pointer arithmetic inside CD3DGlyphBank::RectFillAlpha, producing an out-of-bounds write - the vendor advisory also tags this as a buffer overflow. The affected component is therefore Windows-only and architecture-independent (all architectures listed), and the practical attack surface is the document parser/renderer rather than a network service: an application must parse and draw untrusted XPS content for the overflow to be reached. The CWE-190 root cause combined with C:H/I:H/A:H reflects total technical impact on the hosting process, but the assessed vector retains UI:R, meaning the attacker cannot trigger it without the victim opening the crafted document. The GitHub advisory for the same issue (GHSA-f63g-mx39-3r38) is the authoritative source-code-level description, and the underlying issue is tracked upstream at dotnet/wpf issue 12020.
Know when Windows 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:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Document is delivered over the network (AV:N) and reliably triggered (AC:L) without privileges (PR:N) but needs the victim to open it (UI:R); memory corruption yields full RCE impact (C:H/I:H/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Integer overflow or wraparound in .NET Framework allows an unauthorized attacker to elevate privileges over a network.
Technical POC Analysis
Evidence base: GitHub Security Advisory GHSA-f63g-mx39-3r38 only.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Microsoft's WPF desktop stack, shared by .NET and .NET Framework, contains a memory corruption vulnerability that an unauthenticated, network-positioned attacker can trigger when a user opens a malicious XPS document, potentially leading to remote code execution or privilege elevation and impacting confidentiality, integrity, and availability on affected Windows desktops. Patch available per vendor advisory; no public exploit identified at time of analysis. Organizations with applications that render untrusted XPS content should prioritize remediation because a successful attack could disrupt operations or expose sensitive data.
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.
Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
EUVD-2026-100200
GHSA-f63g-mx39-3r38
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB