Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious XPS content
-
DeliveryVictim opens in WPF application
-
ExploitSynthetic hyperlink bypasses navigation checks
-
ExecutionReach attacker-controlled content
-
ImpactExecute code in user context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access 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 Windows WPF application built on an affected Microsoft.WindowsDesktop.App.Runtime version (8.0.0-8.0.31, 9.0.0-9.0.20, 10.0.x before 10.0.13, or 11.0.0-preview.1-rc.1) that renders XPS content exposed through UI Automation. The attacker must get a victim to interact with attacker-supplied content (UI:R) so that a synthetic hyperlink bypasses the app's restrictive navigation checks and reaches attacker-controlled content. Limiting factors: exploitation is client-side and Windows-only, depends on the victim running a vulnerable WPF/XPS app and performing the interaction, and succeeds only against unpatched runtime versions; it is not a server-side or zero-click vector despite PR:N. |
| Impact | This is a genuinely serious but interaction-gated vulnerability rather than a mass-exploitable network worm. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, score 8.8) shows network reach, low complexity, and no privileges required, but the UI:R flag is decisive: a user must interact (e.g., open attacker-supplied content in a vulnerable WPF application) before code runs. No EPSS score was provided, this CVE is not listed in CISA KEV, and no public exploit was supplied, so exploitation status is 'no public exploit identified at time of analysis.' Note a signal conflict worth verifying: the NVD-style description and CWE-502 frame this as deserialization of untrusted data, while the authoritative dotnet/wpf GHSA advisory describes the actual mechanism as WPF XPS synthetic hyperlinks exposed through UI Automation bypassing restrictive navigation checks to reach attacker-controlled content - the deserialization label and the advisory's navigation-bypass narrative do not cleanly align, so defenders should treat the GHSA advisory as the ground truth for mitigation. Overall this warrants prompt patching for any Windows desktop fleet running WPF apps on affected .NET runtimes, but the mandatory user interaction and desktop-only (client-side) exposure make it a lower immediate priority than an unauthenticated server-side RCE of the same score. |
| Exploit ScenarioDerived | An attacker crafts a malicious XPS document or content containing a synthetic hyperlink and lures a victim into opening or interacting with it inside a WPF application built on an affected Microsoft.WindowsDesktop.App.Runtime version. The synthetic hyperlink exposed via UI Automation bypasses the application's restrictive navigation checks and reaches attacker-controlled content, resulting in code execution in the context of the user running the app. No public exploit code was identified at time of analysis, and user interaction (UI:R) is required for the chain to complete. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Remote code execution affects Windows desktop applications built on the Microsoft.WindowsDesktop.App.Runtime (WPF) component of .NET, specifically runtimes 8.0.0 through 8.0.31, 9.0.0 through 9.0.20, 10.0.0 through 10.0.12, and 11.0.0-preview.1 through 11.0.0-rc.1, as well as Visual Studio 2022 17.14 and Visual Studio 2026 18.10 installations that carry the vulnerable runtime. An unauthenticated attacker can deliver crafted content that, when a victim interacts with an XPS document whose synthetic hyperlinks are exposed through UI Automation, bypasses the application's restrictive navigation checks and reaches attacker-controlled content, leading to code execution in the context of the running application; the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) confirms high confidentiality, integrity, and availability impact but explicitly requires user interaction. Vendor patches are available (runtime fixes 8.0.32, 9.0.21, 10.0.13, and 11.0.0-rc.2), and no public exploit code was identified at time of analysis despite the network-reachable attack path.
RemediationAI
Vendor-released patch: update the Microsoft.WindowsDesktop.App.Runtime packages (win-x64, win-x86, win-arm64) to 8.0.32, 9.0.21, 10.0.13, or 11.0.0-rc.2 depending on the release train in use, and update Visual Studio 2022 17.14 to 17.14.42 and Visual Studio 2026 18.10 to 18.10.4; rebuild and redeploy self-contained or framework-dependent WPF applications so the corrected runtime is actually carried or referenced, since patching a machine's shared runtime does not fix apps that bundle an older Microsoft.WindowsDesktop.App.Runtime. Guidance is published at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-87697 and https://github.com/dotnet/wpf/security/advisories/GHSA-c27m-942f-rcfh. Where immediate upgrades are not possible, compensating controls should target the interaction precondition and the XPS/automation surface: block or quarantine XPS (.xps, .oxps) and XPS-based document containers at email gateways and download proxies (side effect: legitimate paper-spec documents must be routed through an approval or conversion workflow); remove file-type associations and handlers that open XPS content from untrusted sources; avoid running WPF document viewers with UI Automation providers exposed to untrusted documents, or restrict automation access to trusted callers (side effect: accessibility tooling and RPA/automation clients may lose functionality); and run document-viewing applications with reduced privileges and WDAC/AppLocker policies that prevent child-process spawning from viewer binaries (side effect: legitimate plug-in and auto-update workflows from those binaries may break); instruct users not to open XPS attachments or links from unknown senders, since the flaw requires user interaction. Note that the missing patch data for any unlisted runtime build is an absence of information, not a confirmation of safety - verify the exact Microsoft.WindowsDesktop.App.Runtime version in each deployed application manifest.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 9 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 root cause class is CWE-502, Deserialization of Untrusted Data, occurring inside Windows Presentation Foundation's XPS (XML Paper Specification) handling pipeline rather than in a general-purpose serializer such as BinaryFormatter. XPS packages can carry synthetic (non-rendered) hyperlink elements that are nevertheless surfaced to accessibility and automation consumers through UI Automation; because those synthetic links are not validated by the same restrictive navigation checks applied to visible document links, an attacker who controls the document can steer the host application toward attacker-controlled content, which is then processed in a way that permits code execution. The affected artifacts are the platform-specific runtime packages Microsoft.WindowsDesktop.App.Runtime.win-x64, win-x86, and win-arm64 distributed via NuGet, which ship as part of the .NET 8, 9, 10, and 11 (preview/RC) release trains and are consumed by WPF applications and by Visual Studio 2022 17.14 and Visual Studio 2026 18.10. The assessed vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H confirms that no privileges or authentication are needed to trigger the flaw and that the scope remains unchanged, but that the attacker must recruit a victim to interact with the malicious document; exploitation is therefore client-side, Windows-only, and gated on a vulnerable runtime being present - not a server-side or zero-click vector despite the PR:N rating.
Know when .NET 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
Attacker-supplied content is delivered over the network (AV:N) and needs no privileges (PR:N), but a victim must interact with it (UI:R), yielding full code execution in the user context (C:H/I:H/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Deserialization of untrusted data in .NET allows an unauthorized attacker to execute code over a network.
Technical POC Analysis
Evidence base: GHSA-c27m-942f-rcfh only.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Latest POC
1 public PoC link from github
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
CVE-2026-87697 is a high-severity remote code execution flaw in the .NET WPF runtime used by many Windows desktop applications and Visual Studio installations. An unauthenticated attacker can compromise a user's session if the user opens a specially crafted XPS document, but the attack requires user interaction and no public exploit identified at time of analysis. Leadership should prioritize patching affected developer workstations and business-critical desktop applications to prevent potential data loss, operational disruption, and lateral movement from compromised endpoints.
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
Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.
Changjetong T+ (through 16.x) has .NET deserialization RCE in an AjaxPro endpoint. Attacker-controlled JSON triggers des
SQL injection (CWE-89) in Marten, the .NET transactional document DB and event store for PostgreSQL, affects versions 7.
Argument injection in the CliInvoke .NET process-wrapping library (and its former identity, AlastairLundy.CliInvoke) all
SD.NET RIM versions before 4.7.3c contain a SQL injection vulnerability that allows attackers to inject malicious SQL st
PowerDocu versions prior to 2.4.0 allow arbitrary .NET object instantiation and code execution through unsafe deserializ
Weak authentication in ASP.NET Core & Visual Studio allows an unauthorized attacker to elevate privileges over a net
NanaZip versions 5.0.1252.0 through 6.0.1629.0 contain an out-of-bounds heap read in the .NET Single File bundle parser
Out-of-bounds memory read in NanaZip versions 5.0.1252.0 through 6.0.1637.x allows local authenticated attackers to disc
DotNetNuke 9.5 contains a persistent cross-site scripting vulnerability that allows normal users to upload malicious XML
Asp.Net-Core-Inventory-Order-Management-System versions up to 9.20250118. contains a security vulnerability (CVSS 6.3).
Remote code execution in the ActiveMQ NMS AMQP .NET client affects all releases up to and including 2.3.0 when the clien
Remote code execution in .NET WPF (Microsoft.WindowsDesktop.App.Runtime) allows an unauthenticated attacker to execute c
EUVD-2026-99638
GHSA-c27m-942f-rcfh
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB