Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilitywidely-deployed-product-advisoryendpoint-software-vulnerability

Microsoft Issues .NET Security Update to Fix Blazor Debugger Code Execution

Vulnerability Disclosure · 4 sources · Updated 18d ago · First seen Oct 28, 2026

Microsoft Issues .NET Security Update to Fix Blazor Debugger Code Execution

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.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Oct 13, 2026 – Oct 25, 2026
  1. Oct 25, 202624d ago

    Microsoft releases out-of-band .NET fixes and corrects debugger packages

    Microsoft released an out-of-band .NET 10 update with additional SocketAsyncEventArgs, Blazor debugger, source-build tarball ownership, and Brotli fixes, including corrected BrowserDebugHost packaging. Its revised CVE-2026-102870 advisory identified patched debugger packages 10.0.14 and 11.0.0-rc.3.26522.148 and clarified that affected application package references must be updated separately from the runtime.

    .NET 10.0 Update - October 25, 2026 | Microsoft Support
  2. Reported Oct 22, 202627d ago

    Monaco AMSN publishes notice covering multiple .NET vulnerabilities

    Monaco's AMSN published notice CERTFR-2026-AVI-1382 covering multiple vulnerabilities across .NET 8, 9, 10, and 11 installations and certain Linux tarball distributions. The notice directed users to Microsoft's security bulletins for fixes.

    CERTFR-2026-AVI-1382_Multiples vulnérabilités dans Microsoft .Net
  3. Reported Oct 13, 20261mo ago

    Amazon Linux releases .NET 8 and .NET 10 fixes for CVE-2026-102870

    Amazon Linux released fixes for CVE-2026-102870 in Amazon Linux 2023 packages dotnet10.0 and dotnet8.0 under advisories ALAS2023-2026-3366 and ALAS2023-2026-3367. The tracker lists dotnet9.0 and Amazon Linux 2027 Preview dotnet10.0 as pending fixes, with no fix planned for Amazon Linux 2023 dotnet6.0.

    CVE-2026-102870
  4. Oct 13, 20261mo ago

    Microsoft issues October security release and discloses Blazor debugger RCE

    Microsoft issued its October security release and initially published the advisory for CVE-2026-102870, a high-severity Blazor WebAssembly debugger code-injection vulnerability. Attacker-controlled application values could trigger code execution on a developer's machine when the developer evaluates a debugger expression.

    .NET 10.0 Update - October 25, 2026 | Microsoft Support
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.