Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-fx4q-gjrx-2jw6
Microsoft.WindowsDesktop.App.Runtime.win-x86Microsoft.WindowsDesktop.App.Runtime.win-x64Microsoft.WindowsDesktop.App.Runtime.win-x64Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in Windows Presentation Foundation. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
An integer overflow or wraparound in .NET allows an unauthorized attacker to execute code locally.
Announcement
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/434
CVSS Details
- Version: 3.1
- Severity: High
- Score: 7.0
- Vector:
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C - Weakness: CWE-190: Integer Overflow or Wraparound
Affected Platforms
- Platforms: Windows
- Architectures: All
<a name="affected-packages"></a>Affected Packages
The vulnerability affects any Microsoft .NET project if it uses any of affected package versions listed below
<a name=".NET 10"></a>.NET 10
Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.WindowsDesktop.App.Runtime.win-arm64 | >= 10.0.0, <= 10.0.10 | 10.0.11 Microsoft.WindowsDesktop.App.Runtime.win-x64 | >= 10.0.0, <= 10.0.10 | 10.0.11 Microsoft.WindowsDesktop.App.Runtime.win-x86 | >= 10.0.0, <= 10.0.10 | 10.0.11
<a name=".NET 9"></a>.NET 9
Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.WindowsDesktop.App.Runtime.win-arm64 | >= 9.0.0, <= 9.0.18 | 9.0.19 Microsoft.WindowsDesktop.App.Runtime.win-x64 | >= 9.0.0, <= 9.0.18 | 9.0.19 Microsoft.WindowsDesktop.App.Runtime.win-x86 | >= 9.0.0, <= 9.0.18 | 9.0.19
<a name=".NET 8"></a>.NET 8
Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.WindowsDesktop.App.Runtime.win-arm64 | >= 8.0.0, <= 8.0.29 | 8.0.30 Microsoft.WindowsDesktop.App.Runtime.win-x64 | >= 8.0.0, <= 8.0.29 | 8.0.30 Microsoft.WindowsDesktop.App.Runtime.win-x86 | >= 8.0.0, <= 8.0.29 | 8.0.30
Advisory FAQ
<a name="how-affected"></a>How do I know if I am affected?
If using a package listed in affected packages, an application is exposed to the vulnerability.
<a name="how-fix"></a>How do I fix the issue?
- To fix the issue please install the latest version of .NET. If users have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt them to update Visual Studio, which will also update their .NET SDKs.
- If a user's application references the vulnerable package, update the package reference to the patched version. Users can list the versions they have installed by running the
dotnet --infocommand.
Once users have installed the updated runtime or SDK, they should restart their apps for the update to take effect.
Additionally, if they'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 users 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
Users 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. Users 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
Acknowledgements
41ae55e9310ff27fa6f26af4727e5590
Revisions
V1.0 (08/11/2026): Advisory published.
Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.
Drag and drop some file here, or click to select
The vulnerability requires local access to the device to be exploited. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker does not need any special privileges or access rights. The attacker needs the user to perform some action, like clicking a link. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data. There is a high impact on the availability of the system.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard