Skip to main content
Mallory
HighVulnerability

CVE-2026-102870: Blazor WebAssembly Debugger Code Injection and Remote Code Execution

Published Oct 13, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days46 mentions · peak 6 in a dayToday
CVSS8.8High · v3.1
EPSS0.91%60th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-102870CWE-94 · Improper Control of Generation of…

CVE-2026-102870 is a code-injection vulnerability in the ASP.NET Core Blazor WebAssembly debugger bundled with Microsoft.AspNetCore.Components.WebAssembly.Server and Microsoft.AspNetCore.Components.WebAssembly.DevServer. The debug proxy evaluates debugger expressions by generating and compiling C# source. Application-derived values, including ToString() results, descriptions, and class names, are embedded without consistent escaping, allowing malicious values to escape generated string literals and introduce executable code. Exploitation occurs when a developer evaluates an expression involving attacker-controlled application data. Affected package versions are 10.0.0 through versions earlier than 10.0.14, and 11.0.0-preview.1 through versions earlier than 11.0.0-rc.3.26522.148. The vulnerability affects Windows, Linux, and macOS across all architectures.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation executes arbitrary code on the developer's machine in the developer's security context, potentially compromising accessible sensitive information, modifying applications or other data, and disrupting the development environment. Microsoft assigns a CVSS v3.1 base score of 8.8, with high confidentiality, integrity, and availability impacts. Exploitation requires debugger interaction; this is not an interaction-free compromise of a production ASP.NET Core application.

Mitigation

If you can’t patch tonight, do this now.

Until corrected packages are installed, avoid evaluating debugger expressions or inspecting objects involving untrusted or attacker-controlled application data with the affected Blazor WebAssembly debugger. This precaution follows from the exploitation prerequisites; no separate vendor workaround is specified.

Remediation

Patch, then assume compromise.

Update every affected Microsoft.AspNetCore.Components.WebAssembly.Server and Microsoft.AspNetCore.Components.WebAssembly.DevServer package reference to 10.0.14 or a later supported release for .NET 10, or 11.0.0-rc.3.26522.148 or a later applicable release for .NET 11. Install the latest supported .NET SDK and applicable distribution security updates. Updating only the shared runtime does not replace vulnerable standalone debugger package references. Restart the debugger and development environment after updating. Apply the corrected out-of-band updates even if the initial October 13, 2026 security update was installed, because the original fix had incomplete debugger packaging. Ubuntu installations updated under USN-8942-1 require the corrected updates in USN-8958-1 or their successors.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft Corporation.Net 10.0 Installed On Linuxapplication
Microsoft Corporation.Net 10.0 Installed On Mac Osapplication
Microsoft Corporation.Net 10.0 Installed On Windowsapplication
Microsoft Corporation.Net 11.0 Installed On Linuxapplication
Microsoft Corporation.Net 11.0 Installed On Mac Osapplication
Microsoft Corporation.Net 11.0 Installed On Windowsapplication
Microsoft CorporationMicrosoft Visual Studio 2019 Version 16.11application
Microsoft CorporationMicrosoft Visual Studio 2026 Version 18.10application
Microsoft CorporationMicrosoft Visual Studio 2026 Version 18.11application
Microsoft CorporationMicrosoft Visual Studio 2026 Version 18.12application
Microsoft CorporationMicrosoft.Aspnetcore.Components.Webassembly.Devserverapplication
Microsoft CorporationMicrosoft.Aspnetcore.Components.Webassembly.Serverapplication
Microsoft CorporationVisual Studio 2022application
FAQ

Frequently asked questions

Is CVE-2026-102870 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-102870 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-102870?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-102870.
Is there a patch for CVE-2026-102870?
Update every affected Microsoft.AspNetCore.Components.WebAssembly.Server and Microsoft.AspNetCore.Components.WebAssembly.DevServer package reference to 10.0.14 or a later supported release for .NET 10, or 11.0.0-rc.3.26522.148 or a later applicable release for .NET 11. Install the latest supported .NET SDK and applicable distribution security updates.
What products are affected by CVE-2026-102870?
Microsoft Corporation Microsoft.Aspnetcore.Components.Webassembly.Devserver, Microsoft Corporation Microsoft.Aspnetcore.Components.Webassembly.Server, Microsoft Corporation Microsoft Visual Studio 2019 Version 16.11, Microsoft Corporation Microsoft Visual Studio 2026 Version 18.10, Microsoft Corporation Microsoft Visual Studio 2026 Version 18.11, and 8 more.
How severe is CVE-2026-102870?
CVE-2026-102870 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.91% (60th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

55 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+42 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity7Community discussion across Reddit, Mastodon, and other social sources.