CVE-2026-102870: ASP.NET Core Remote Code Execution Vulnerability
Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in the Blazor WebAssembly debugger included in Microsoft.AspNetCore.Components.WebAssembly.Server. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
The Blazor WebAssembly debug proxy evaluates debugger expressions by generating and compiling C# source. Certain values originating in the application being debugged, including ToString() results, descriptions, and class names, are embedded in that generated source without consistent escaping. An attacker-controlled value can escape the generated string literal and execute code on a developer's machine when the developer evaluates an expression during debugging.
Announcement
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/445
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-94 (Improper Control of Generation of Code ('Code Injection'))
Affected Platforms
- Platforms: Windows, Linux, macOS - 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.AspNetCore.Components.WebAssembly.Server | >= 10.0.0, <= 10.0.12 | 10.0.13 Microsoft.AspNetCore.Components.WebAssembly.Server | >= 11.0.0-preview.1, <= 11.0.0-rc.1 | 11.0.0-rc.2.26478.115
Advisory FAQ
<a name="how-affected"></a>How do I know if I am affected?
You are affected if you use a vulnerable version of Microsoft.AspNetCore.Components.WebAssembly.Server to debug a Blazor WebAssembly application and evaluate an expression involving attacker-controlled application data.
<a name="how-fix"></a>How do I fix the issue?
1. Install the latest supported version of .NET. 2. Update Microsoft.AspNetCore.Components.WebAssembly.Server to the patched version for the .NET release used by the application.
Once the updated package or runtime is installed, restart the debugger and development environment.
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 repositories are located at https://github.com/dotnet/runtime and https://github.com/dotnet/aspnetcore. The Announcements repository (https://github.com/dotnet/announcements) will contain this bulletin as an issue and will include a link to a 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-102870
Acknowledgements
alittleston3
Revisions
V1.0 (10/13/2026): Advisory published.
Other sources
ASP.NET Core Remote Code Execution Vulnerability
— Microsoft
Improper control of generation of code ('code injection') in ASP.NET Core allows an unauthorized attacker to execute code over a network.
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.13 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 18.10.4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 11.0.0-rc.2.26478.115 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 17.14.42 - Upgrade
Upgrade
nuget/Microsoft.AspNetCore.Components.WebAssembly.Serverto a version that resolves this vulnerability.Fixed in 11.0.0-rc.2.26478.115 - Upgrade
Upgrade
nuget/Microsoft.AspNetCore.Components.WebAssembly.Serverto a version that resolves this vulnerability.Fixed in 10.0.13 - Upgrade
Upgrade
Microsoft.AspNetCore.Components.WebAssembly.Serverto a version that resolves this vulnerability.Fixed in 10.0.13 - Upgrade
Upgrade
Microsoft.AspNetCore.Components.WebAssembly.Serverto a version that resolves this vulnerability.Fixed in 11.0.0-rc.2.26478.115 - Operational
After installing the updated package or runtime, restart the debugger and development environment.
Event History
Frequently Asked Questions
What level of access and interaction does an attacker need?
The CVSS vector indicates that exploitation can be performed over a network with low attack complexity and no privileges required. User interaction is required.
Which Microsoft software should be included in impact review?
Review deployments of Microsoft ASP.NET Core and Microsoft.AspNetCore.Components.WebAssembly.Server, as well as environments using Microsoft Visual Studio 2022 or Microsoft Visual Studio 2026.