| Package | Affected versions | Patched versions |
|---|---|---|
| Microsoft.WindowsDesktop.App.Runtime.win-arm64 | ≥ 10.0.0, < 10.0.11≥ 8.0.0, < 8.0.30≥ 9.0.0, < 9.0.19 | 10.0.118.0.309.0.19 |
| Microsoft.WindowsDesktop.App.Runtime.win-x64 | ≥ 10.0.0, < 10.0.11≥ 8.0.0, < 8.0.30≥ 9.0.0, < 9.0.19 | 10.0.118.0.309.0.19 |
| Microsoft.WindowsDesktop.App.Runtime.win-x86 | ≥ 10.0.0, < 10.0.11≥ 8.0.0, < 8.0.30≥ 9.0.0, < 9.0.19 | 10.0.118.0.309.0.19 |
| .net | ≥ 10.0.0, < 10.0.11≥ 8.0.0, < 8.0.30≥ 9.0.0, < 9.0.19 | 10.0.118.0.309.0.19 |
| .net framework | = 3.5= 4.6.2= 4.7= 4.7.1= 4.7.2= 4.8= 4.8.1 | |
| visual studio 2022 | ≥ 17.14.0, < 17.14.38 | 17.14.38 |
| visual studio 2026 | ≥ 18.8.0, < 18.8.3 | 18.8.3 |
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 out-of-bounds write in .NET allows an unauthorized attacker to execute code locally.
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/432
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:CThe vulnerability affects any Microsoft .NET project if it uses any of affected package versions listed below
| 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 |
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.WindowsDesktop.App.Runtime.win-arm64 |
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free| >= 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 |
| 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 |
If using a package listed in affected packages, an application is exposed to the vulnerability.
dotnet --info command.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.
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.
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.
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.
V1.0 (08/11/2026): Advisory published.