Microsoft Security Advisory CVE-2026-70007 - .NET and Visual Studio Remote Code Execution Vulnerability
The source advisory has changed since this explanation was prepared. Check the current technical data and original advisory below.
Executive Summary
Microsoft has released a security advisory regarding a vulnerability in Microsoft.WindowsDesktop.App.Runtime (WPF). Crafted WPF pixel-shader bytecode can desynchronize the two parsing passes in CPSTrans::Initialize, leading to heap out-of-bounds writes or reads.
Announcement
The official announcement for this issue is available at https://github.com/dotnet/announcements/issues/450.
CVSS Details
- Version: 3.1
- Severity: High
- Score: 8.8
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Weakness: CWE-787 (Out-of-bounds Write)
Affected Platforms
- Platforms: Windows
- Architectures: All
Affected Packages
This vulnerability affects Microsoft .NET projects using any of the package versions listed below:
Advisory FAQ
How do I know if I am affected?
If you are using any package version listed in the Affected Packages table, your project is exposed to the vulnerability.
How do I fix the issue?
-
- To resolve the issue, install the latest version of .NET. If you installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to apply an update, which will update your .NET SDKs as well.
-
- If your application references a vulnerable package, update the reference to the patched version. You can check the installed versions by executing the
dotnet --infocommand.
- If your application references a vulnerable package, update the reference to the patched version. You can check the installed versions by executing the
After installing the updated runtime or SDK, restart your applications for the changes to take effect.
In addition, if you have deployed self-contained applications) targeting any of the affected versions, those applications are also vulnerable and must be recompiled and redeployed.
Other Information
Reporting Security Issues
If you discover a potential security issue in a supported version of .NET, report it to the Microsoft Security Response Center (MSRC) using the MSRC Researcher Portal.). Additional details are provided in the MSRC Report an Issue FAQ.).
Reports submitted through the MSRC may qualify for the Microsoft .NET Bounty. Details and program terms are available at https://aka.ms/corebounty..
Support
Questions regarding this advisory can be submitted on GitHub within the .NET GitHub organization. The primary repositories are located at https://github.com/dotnet/runtime.. The Announcements repository (https://github.com/dotnet/Announcements)) includes this bulletin as an issue with a link to a dedicated discussion issue.
Disclaimer
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
External Links
Acknowledgements
- phrolo7a
- Muhammad Abdul Rehman
- SOMESH SONUNE
- Matheus Siqueira
- thegoldmandm
- Aobo Wang (@m4x_1997)
- Mateusz Gierblinski with Curios (https://curios-it.eu/))
- m0ssser (https://m0ssser-portfolio.pages.dev/))
- Alex Hannah
Revisions
V1.0 (10/13/2026): Advisory published.
What to do
-
- Install the latest version of .NET. If .NET SDKs were installed via Visual Studio, accept the update prompt in Visual Studio to update the SDKs.
-
- If your application directly references an affected package, update the dependency to the patched version. Use the
dotnet --infocommand to list installed package versions.
- If your application directly references an affected package, update the dependency to the patched version. Use the
- Restart applications after installing the updated runtime or SDK.
- Recompile and redeploy any self-contained applications) targeting the vulnerable runtime versions.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| .NET (NuGet) | Microsoft.WindowsDesktop.App.Runtime.win-arm64 | >= 9.0.0, < 9.0.21, >= 11.0.0-preview.1, < 11.0.0-rc.2, >= 10.0.0, < 10.0.13, >= 8.0.0, < 8.0.32 | 9.0.21, 11.0.0-rc.2, 10.0.13, 8.0.32 |
| .NET (NuGet) | Microsoft.WindowsDesktop.App.Runtime.win-x64 | >= 9.0.0, < 9.0.21, >= 11.0.0-preview.1, < 11.0.0-rc.2, >= 10.0.0, < 10.0.13, >= 8.0.0, < 8.0.32 | 9.0.21, 11.0.0-rc.2, 10.0.13, 8.0.32 |
| .NET (NuGet) | Microsoft.WindowsDesktop.App.Runtime.win-x86 | >= 9.0.0, < 9.0.21, >= 11.0.0-preview.1, < 11.0.0-rc.2, >= 10.0.0, < 10.0.13, >= 8.0.0, < 8.0.32 | 9.0.21, 11.0.0-rc.2, 10.0.13, 8.0.32 |
References
- https://github.com/dotnet/wpf/security/advisories/GHSA-pfwj-2f93-rf42
- https://github.com/dotnet/announcements/issues/450
- https://github.com/dotnet/wpf/issues/12016
- https://github.com/dotnet/wpf
- https://nvd.nist.gov/vuln/detail/CVE-2026-70007
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70007
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H- Weakness (CWE)
CWE-787- Platform
- .NET (NuGet)
- Package
Microsoft.WindowsDesktop.App.Runtime.win-arm64, Microsoft.WindowsDesktop.App.Runtime.win-x64, Microsoft.WindowsDesktop.App.Runtime.win-x86- Disclosed
- 13.10.2026
- Updated
- 19.10.2026 22:17
Sources and licenses · Edited or translated by DockRay; source rights and applicable licenses are retained.
OSV / GitHub Advisory Database - GHSA-pfwj-2f93-rf42 - CC BY 4.0
Vulnerability history: Microsoft.WindowsDesktop.App.Runtime.win-arm64
All published vulnerabilities of this package (.NET (NuGet)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 19
- First → latest
- 12.2022 10.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- High 16
- Medium 3
Disclosures per year
- 2022: 1
- 2023: 2
- 2024: 1
- 2025: 0
- 2026: 15
-
Microsoft Security Advisory CVE-2026-70007 - .NET and Visual Studio Remote Code Execution Vulnerability this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.