| パッケージ | 影響を受けるバージョン | 修正済みバージョン |
|---|---|---|
| Microsoft.WindowsDesktop.App.Runtime.win-arm64 | ≥ 10.0.0, < 10.0.10≥ 8.0.0, < 8.0.29≥ 9.0.0, < 9.0.18 | 10.0.108.0.299.0.18 |
| Microsoft.WindowsDesktop.App.Runtime.win-x64 | ≥ 10.0.0, < 10.0.10≥ 8.0.0, < 8.0.29≥ 9.0.0, < 9.0.18 | 10.0.108.0.299.0.18 |
| Microsoft.WindowsDesktop.App.Runtime.win-x86 | ≥ 10.0.0, < 10.0.10≥ 8.0.0, < 8.0.29≥ 9.0.0, < 9.0.18 | 10.0.108.0.299.0.18 |
| .net | ≥ 8.0.0, < 8.0.29≥ 9.0.0, < 9.0.18 | 8.0.299.0.18 |
| .net framework | = 3.5= 4.6.2= 4.7= 4.7.1= 4.7.2= 4.8= 4.8.1 | |
| visual studio 2022 | ≥ 17.12.0, < 17.12.22≥ 17.14.0, < 17.14.36 | 17.12.2217.14.36 |
| visual studio 2026 | ≥ 18.7.0, < 18.7.4 | 18.7.4 |
Microsoft is releasing this security advisory to provide information about a vulnerability in Windows Presentation Foundation (WPF). This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A remote code execution vulnerability exists in Windows Presentation Foundation (WPF) in .NET 8, .NET 9, and .NET 10 when parsing specially crafted XAML input. An attacker who successfully exploits this vulnerability could execute arbitrary code in the context of the current user.
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/**TBD**
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HThe 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.9 | 10.0.10 |
| Microsoft.WindowsDesktop.App.Runtime.win-x64 | >= 10.0.0, <= 10.0.9 | 10.0.10 |
| Microsoft.WindowsDesktop.App.Runtime.win-x86 | >= 10.0.0, <= 10.0.9 | 10.0.10 |
| Package name | Affected version | Patched version |
|---|
これらの製品をお使いですか？サイトをスキャンして、脆弱なバージョンが公開されていないか確認しましょう。
無料でサイトをスキャン| Microsoft.WindowsDesktop.App.Runtime.win-arm64 | >= 9.0.0, <= 9.0.17 | 9.0.18 |
| Microsoft.WindowsDesktop.App.Runtime.win-x64 | >= 9.0.0, <= 9.0.17 | 9.0.18 |
| Microsoft.WindowsDesktop.App.Runtime.win-x86 | >= 9.0.0, <= 9.0.17 | 9.0.18 |
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.WindowsDesktop.App.Runtime.win-arm64 | >= 8.0.0, <= 8.0.28 | 8.0.29 |
| Microsoft.WindowsDesktop.App.Runtime.win-x64 | >= 8.0.0, <= 8.0.28 | 8.0.29 |
| Microsoft.WindowsDesktop.App.Runtime.win-x86 | >= 8.0.0, <= 8.0.28 | 8.0.29 |
If using a package listed in affected packages, developers exposed to the vulnerability.
dotnet --info command.Once developers 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 anyone has 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.
Direct questions about this issue to 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.
Kevin Gosse, 41ae55e9310ff27fa6f26af4727e5590, Ky0toFu
V1.0 (July 14, 2026): Advisory published.