Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-102870 high CVSS 8.8

Code Injection in Microsoft.AspNetCore.Components.WebAssembly.Server (CVE-2026-102870)

Summary

Code injection in Microsoft.AspNetCore.Components.WebAssembly.Server (CVE-2026-102870). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 11.0.0-rc.2.26478.115 or later.

Original description

The description as published by the source.

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

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.Serv…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-102870 has been found in Microsoft.AspNetCore.Components.WebAssembly.Server.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade Microsoft.AspNetCore.Components.WebAssembly.Server to 11.0.0-rc.2.26478.115 or later.
If unsure, ask your IT team or search "Microsoft.AspNetCore.Components.WebAssembly.Server CVE-2026-102870" on the vendor's site.

CVE-2026-102870 (Microsoft.AspNetCore.Components.WebAssembly.Server) — CWE-94 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Patched: 11.0.0-rc.2.26478.115 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Arbitrary code execution (CWE-94) exists in Microsoft.AspNetCore.Components.WebAssembly.Server.

📍 Affected scope

Check the vendor advisory for the affected versions of Microsoft.AspNetCore.Components.WebAssembly.Server.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 11.0.0-rc.2.26478.115.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Microsoft.AspNetCore.Components.WebAssembly.Server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'Microsoft.AspNetCore.Components.WebAssembly.Server' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Microsoft.AspNetCore.Components.WebAssembly.Server を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade Microsoft.AspNetCore.Components.WebAssembly.Server to 11.0.0-rc.2.26478.115

    ステージング環境で 11.0.0-rc.2.26478.115 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

nuget Microsoft.AspNetCore.Components.WebAssembly.Server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"11.0.0-rc.2.26478.115"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details