Microsoft Issues .NET Security Update to Fix Blazor Debugger Code Execution
Vulnerability Disclosure · 4 sources · Updated 18d ago · First seen Oct 28, 2026

Microsoft released an out-of-band .NET 10.0 security update on October 25, adding fixes beyond its October 13 release and correcting BrowserDebugHost packaging for CVE-2026-102870. The high-severity vulnerability, rated CVSS 8.8, affects the Blazor WebAssembly debugger bundled with Microsoft.AspNetCore.Components.WebAssembly.Server and Microsoft.AspNetCore.Components.WebAssembly.DevServer. Insufficient escaping of attacker-controlled application values in generated C# source can allow code execution on a developer’s machine when the developer evaluates a debugger expression. Affected .NET 10 and .NET 11 packages span Windows, Linux, and macOS.
Updating the shared runtime alone does not remediate affected Blazor applications. Development teams must update the affected package references to 10.0.14 or 11.0.0-rc.3.26522.148, as applicable, and restart the debugger and development environment. Microsoft advises affected customers to install the latest update even if they applied the October 13 release; the .NET 10.0 update also addresses SocketAsyncEventArgs memory corruption, source-build tarball ownership, and a Brotli decoder out-of-bounds write. A related CERT-FR notice lists broader .NET exposure across versions 8 through 11, including privilege-escalation risks, and directs users to Microsoft’s fixes.


