GHSA-f63g-mx39-3r38: Integer Overflow
Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in Microsoft.WindowsDesktop.App.Runtime (WPF). This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
Attacker-controlled XPS glyph coordinates can overflow destination pointer arithmetic in CD3DGlyphBank::RectFillAlpha, causing an out-of-bounds write and process termination.
Announcement
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/469
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-190 (Integer Overflow or Wraparound) Affected Platforms
- Platforms: Windows - Architectures: All
<a name="affected-packages"></a>Affected Packages
The vulnerability affects Microsoft .NET projects that use an affected package version listed below.
Package name | Affected version | Patched version ------------ | ---------------- | --------------- Microsoft.WindowsDesktop.App.Runtime.win-arm64 | >= 8.0.0, <= 8.0.31 | 8.0.32 Microsoft.WindowsDesktop.App.Runtime.win-x64 | >= 8.0.0, <= 8.0.31 | 8.0.32 Microsoft.WindowsDesktop.App.Runtime.win-x86 | >= 8.0.0, <= 8.0.31 | 8.0.32 Microsoft.WindowsDesktop.App.Runtime.win-arm64 | >= 10.0.0, <= 10.0.12 | 10.0.13 Microsoft.WindowsDesktop.App.Runtime.win-x64 | >= 10.0.0, <= 10.0.12 | 10.0.13 Microsoft.WindowsDesktop.App.Runtime.win-x86 | >= 10.0.0, <= 10.0.12 | 10.0.13 Microsoft.WindowsDesktop.App.Runtime.win-arm64 | >= 9.0.0, <= 9.0.20 | 9.0.21 Microsoft.WindowsDesktop.App.Runtime.win-x64 | >= 9.0.0, <= 9.0.20 | 9.0.21 Microsoft.WindowsDesktop.App.Runtime.win-x86 | >= 9.0.0, <= 9.0.20 | 9.0.21 Microsoft.WindowsDesktop.App.Runtime.win-arm64 | >= 11.0.0-preview.1, <= 11.0.0-rc.1 | 11.0.0-rc.2 Microsoft.WindowsDesktop.App.Runtime.win-x64 | >= 11.0.0-preview.1, <= 11.0.0-rc.1 | 11.0.0-rc.2 Microsoft.WindowsDesktop.App.Runtime.win-x86 | >= 11.0.0-preview.1, <= 11.0.0-rc.1 | 11.0.0-rc.2
Advisory FAQ
<a name="how-affected"></a>How do I know if I am affected?
If using a package listed in affected packages, you're exposed to the vulnerability.
<a name="how-fix"></a>How do I fix the issue?
1. To fix the issue please install the latest version of .NET. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs. 2. If your application references the vulnerable package, update the package reference to the patched version. You can list the versions you have installed by running the dotnet --info command.
Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.
Additionally, if you've deployed self-contained applications targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.
Other Information
Reporting Security Issues
If you have found a potential security issue in a supported version of .NET, please report it to the Microsoft Security Response Center (MSRC) via the MSRC Researcher Portal. Further information can be found in the MSRC Report an Issue FAQ.
Security reports made through MSRC may qualify for the Microsoft .NET Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.
Support
You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked 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
CVE-2026-85363
Acknowledgements
- Ky0toFu (@ky0tofu)
Revisions
V1.0 (10/13/2026): Advisory published.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
nuget/Microsoft.WindowsDesktop.App.Runtime.win-x86to a version that resolves this vulnerability.Fixed in 11.0.0-rc.2 - Upgrade
Upgrade
nuget/Microsoft.WindowsDesktop.App.Runtime.win-x64to a version that resolves this vulnerability.Fixed in 11.0.0-rc.2 - Upgrade
Upgrade
nuget/Microsoft.WindowsDesktop.App.Runtime.win-arm64to a version that resolves this vulnerability.Fixed in 11.0.0-rc.2 - Upgrade
Upgrade
nuget/Microsoft.WindowsDesktop.App.Runtime.win-x86to a version that resolves this vulnerability.Fixed in 9.0.21 - Upgrade
Upgrade
nuget/Microsoft.WindowsDesktop.App.Runtime.win-x64to a version that resolves this vulnerability.Fixed in 9.0.21 - Upgrade
Upgrade
nuget/Microsoft.WindowsDesktop.App.Runtime.win-arm64to a version that resolves this vulnerability.Fixed in 9.0.21 - Upgrade
Upgrade
nuget/Microsoft.WindowsDesktop.App.Runtime.win-x86to a version that resolves this vulnerability.Fixed in 10.0.13 - Upgrade
Upgrade
nuget/Microsoft.WindowsDesktop.App.Runtime.win-x64to a version that resolves this vulnerability.Fixed in 10.0.13 - Upgrade
Upgrade
nuget/Microsoft.WindowsDesktop.App.Runtime.win-arm64to a version that resolves this vulnerability.Fixed in 10.0.13 - Upgrade
Upgrade
nuget/Microsoft.WindowsDesktop.App.Runtime.win-x86to a version that resolves this vulnerability.Fixed in 8.0.32 - Upgrade
Upgrade
nuget/Microsoft.WindowsDesktop.App.Runtime.win-x64to a version that resolves this vulnerability.Fixed in 8.0.32 - Upgrade
Upgrade
nuget/Microsoft.WindowsDesktop.App.Runtime.win-arm64to a version that resolves this vulnerability.Fixed in 8.0.32 - Upgrade
Upgrade
Microsoft.WindowsDesktop.App.Runtime.win-arm64, Microsoft.WindowsDesktop.App.Runtime.win-x64, Microsoft.WindowsDesktop.App.Runtime.win-x86to a version that resolves this vulnerability.Fixed in 8.0.32 - Upgrade
Upgrade
Microsoft.WindowsDesktop.App.Runtime.win-arm64, Microsoft.WindowsDesktop.App.Runtime.win-x64, Microsoft.WindowsDesktop.App.Runtime.win-x86to a version that resolves this vulnerability.Fixed in 9.0.21 - Upgrade
Upgrade
Microsoft.WindowsDesktop.App.Runtime.win-arm64, Microsoft.WindowsDesktop.App.Runtime.win-x64, Microsoft.WindowsDesktop.App.Runtime.win-x86to a version that resolves this vulnerability.Fixed in 10.0.13 - Upgrade
Upgrade
Microsoft.WindowsDesktop.App.Runtime.win-arm64, Microsoft.WindowsDesktop.App.Runtime.win-x64, Microsoft.WindowsDesktop.App.Runtime.win-x86to a version that resolves this vulnerability.Fixed in 11.0.0-rc.2 - Upgrade
Upgrade
Microsoft.WindowsDesktop.App.Runtime (WPF)to a version that resolves this vulnerability.Fixed in 8.0.32Patch CVE-2026-85363 - Operational
Recompile and redeploy self-contained applications targeting impacted versions.
- Operational
Restart applications after installing the updated runtime or SDK.
Event History
Frequently Asked Questions
Which deployments should be assessed?
Assess Windows .NET projects that use affected versions of Microsoft.WindowsDesktop.App.Runtime.win-x86, Microsoft.WindowsDesktop.App.Runtime.win-x64, or Microsoft.WindowsDesktop.App.Runtime.win-arm64. All Windows architectures are identified as affected.
What does exploitation require from an attacker?
An attacker needs to supply XPS content with attacker-controlled glyph coordinates and requires user interaction. The CVSS vector indicates exploitation can be performed remotely and does not require attacker privileges.
What is the potential impact of successful exploitation?
The integer overflow can cause an out-of-bounds write and process termination. The advisory assigns high confidentiality, integrity, and availability impacts.
What should developers do to remediate the issue?
Update affected applications to a patched Microsoft.WindowsDesktop.App.Runtime package version identified by the advisory. The provided data does not include the specific affected or patched version numbers.