Security

Microsoft Security Advisory CVE-2026-102870: ASP.NET Core Remote Code Execution Vulnerability

Microsoft has issued an out-of-band security update addressing a high-severity remote code execution vulnerability in the Blazor WebAssembly debugger. The flaw affects specific versions of Microsoft.AspNetCore.Components.WebAssembly.Server and Microsoft.AspNetCore.Components.WebAssembly.DevServer across .NET 10.0 and .NET 11.0 releases.

What changed From the source

Microsoft published a security advisory detailing a remote code execution vulnerability assigned as CVE-2026-102870, with a CVSS score of 8.8 out of 10. The vulnerability resides in the Blazor WebAssembly debug proxy found within Microsoft.AspNetCore.Components.WebAssembly.Server and Microsoft.AspNetCore.Components.WebAssembly.DevServer.

The debug proxy evaluates debugger expressions by generating and compiling C# source code. When expressions are evaluated, certain application-derived values such as class names, descriptions, and ToString results are embedded into the generated code without proper escaping. If a developer evaluates expressions involving attacker-controlled application data during debugging, the untrusted input can escape the string literal and execute code on the local machine.

The flaw impacts Windows, Linux, and macOS platforms across all architectures. Affected package versions and their corresponding patches include:

  • Microsoft.AspNetCore.Components.WebAssembly.Server versions >= 10.0.0 and < 10.0.14 are fixed in version 10.0.14.
  • Microsoft.AspNetCore.Components.WebAssembly.Server versions >= 11.0.0-preview.1 and < 11.0.0-rc.3.26522.148 are fixed in version 11.0.0-rc.3.26522.148.
  • Microsoft.AspNetCore.Components.WebAssembly.DevServer versions >= 10.0.0 and < 10.0.14 are fixed in version 10.0.14.
  • Microsoft.AspNetCore.Components.WebAssembly.DevServer versions >= 11.0.0-preview.1 and < 11.0.0-rc.3.26522.148 are fixed in version 11.0.0-rc.3.26522.148.

At a glance · Security

Affects .NET 10.0, .NET 11.0

What changedWhy it mattersWho should careUpgrade and migration considerations

Why it matters Analysis

This vulnerability targets developer environments rather than production servers directly, but its high CVSS score reflects the severe risk of arbitrary code execution. Because debugging sessions often involve inspecting untrusted data or payloads coming from external sources, a malicious data payload could compromise a developer workstation when evaluated.

The issue stems from insufficient escaping during dynamic C# source generation inside the debug proxy. Remediating this requires explicit package updates rather than simply patching the shared runtime, meaning teams must audit their project dependencies to ensure the risk is fully eliminated.

  • Poses a direct threat to developer workstation security during active debugging sessions.
  • Relies on unsafe string interpolation or generation within the debugging toolchain when handling application data like class names or ToString outputs.

Who should care Analysis

Development teams building Blazor WebAssembly applications on .NET 10.0 or .NET 11.0 are directly impacted if they reference the vulnerable server or development server packages. Developers who routinely inspect complex or untrusted data structures using the debugger are at the highest risk.

Engineering managers and security leads should verify that all local and CI/CD development environments are updated, as shared runtime installations alone will not resolve the vulnerability present in the standalone packages.

  • .NET developers utilizing Blazor WebAssembly debug tooling.
  • Organizations maintaining applications on .NET 10.0 and .NET 11.0 preview or release candidate tracks.

Upgrade and migration considerations Analysis

To address this security advisory, developers must install the latest supported version of .NET and update package references for Microsoft.AspNetCore.Components.WebAssembly.Server or Microsoft.AspNetCore.Components.WebAssembly.DevServer to the patched versions specified in the advisory.

The source explicitly notes that updating only the shared runtime is inadequate. After applying the package updates, developers should restart both their debugger and their development environment to ensure the changes take effect properly.

  • Update package references in project files to version 10.0.14 or 11.0.0-rc.3.26522.148 depending on the active .NET track.
  • Restart the local development environment and debugging tools after completing the package updates.

Sources and further reading

Original: “Microsoft Security Advisory CVE-2026-102870 | ASP.NET Core Remote Code Execution Vulnerability | October 25, 2026 OOB update”, .NET Announcements, published 25 Oct 2026, retrieved 25 Oct 2026. This article was drafted with AI assistance from the official source and passed automated fact and quality checks. Spotted a mistake? See our corrections policy.