CVE-2026-102870
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 0.91 % · percentile 60.44 % · scored 17 Nov 2026.
Saved 17 Nov 2026 15:26:11 UTC · View this risk record (JSON)
No access to your tenant or devices. Every item links to its source. What this means
CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 0.91 % · percentile 60.44 % · scored 17 Nov 2026.
Saved 17 Nov 2026 15:26:11 UTC · View this risk record (JSON)
Improper control of generation of code ('code injection') in ASP.NET Core allows an unauthorized attacker to execute code over a network.
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Improper control of generation of code ('code injection') in ASP.NET Core allows an unauthorized attacker to execute code over a network.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
datePublished: Oct 13, 2026, 7:01:30 PM
dateUpdated: Nov 10, 2026, 8:45:52 PM
RHSA-2026:86192: Red Hat Security Advisory: .NET 10.0 security, bug fix, and enhancement update
CVE-2026-58280 · CVE-2026-66822 · CVE-2026-69651 · CVE-2026-70159 · CVE-2026-70175 · CVE-2026-70179 · CVE-2026-70181 · CVE-2026-70183 · CVE-2026-70186 · CVE-2026-70188 · CVE-2026-70196 · CVE-2026-84008 · CVE-2026-88092 · CVE-2026-92707 · CVE-2026-96225 · CVE-2026-96230 · CVE-2026-96231 · CVE-2026-96233 · CVE-2026-96236 · CVE-2026-96237 · CVE-2026-96238 · CVE-2026-96957 · CVE-2026-96958 · CVE-2026-96959 · CVE-2026-96960 · CVE-2026-102870
RHSA-2026:86193: Red Hat Security Advisory: .NET 10.0 security, bug fix, and enhancement update
CVE-2026-58280 · CVE-2026-66822 · CVE-2026-69651 · CVE-2026-70159 · CVE-2026-70175 · CVE-2026-70179 · CVE-2026-70181 · CVE-2026-70183 · CVE-2026-70186 · CVE-2026-70188 · CVE-2026-70196 · CVE-2026-84008 · CVE-2026-88092 · CVE-2026-92707 · CVE-2026-96225 · CVE-2026-96230 · CVE-2026-96231 · CVE-2026-96233 · CVE-2026-96236 · CVE-2026-96237 · CVE-2026-96238 · CVE-2026-96957 · CVE-2026-96958 · CVE-2026-96959 · CVE-2026-96960 · CVE-2026-102870
NCSC-2026-0426: Kwetsbaarheden verholpen in Microsoft Developer Tools
CVE-2026-58280 · CVE-2026-66822 · CVE-2026-69370 · CVE-2026-69651 · CVE-2026-69905 · CVE-2026-69914 · CVE-2026-69945 · CVE-2026-69969 · CVE-2026-69979 · CVE-2026-70007 · CVE-2026-70035 · CVE-2026-70098 · CVE-2026-70159 · CVE-2026-70161 · CVE-2026-70165 · CVE-2026-70174 · CVE-2026-70175 · CVE-2026-70179 · CVE-2026-70181 · CVE-2026-70183 · CVE-2026-70186 · CVE-2026-70188 · CVE-2026-70190 · CVE-2026-70194 · CVE-2026-70196 · CVE-2026-70197 · CVE-2026-83520 · CVE-2026-84008 · CVE-2026-85363 · CVE-2026-85849 · CVE-2026-85934 · CVE-2026-87697 · CVE-2026-88092 · CVE-2026-96224 · CVE-2026-96225 · CVE-2026-96229 · CVE-2026-96230 · CVE-2026-96231 · CVE-2026-96232 · CVE-2026-96233 · CVE-2026-96234 · CVE-2026-96235 · CVE-2026-96236 · CVE-2026-96237 · CVE-2026-96238 · CVE-2026-96957 · CVE-2026-96958 · CVE-2026-96959 · CVE-2026-96960 · CVE-2026-102229 · CVE-2026-102230 · CVE-2026-102231 · CVE-2026-102232 · CVE-2026-102233 · CVE-2026-102234 · CVE-2026-102235 · CVE-2026-102238 · CVE-2026-102851 · CVE-2026-102870 · CVE-2026-103572 · CVE-2026-108398 · CVE-2026-102869
WID-SEC-W-2026-3893: Microsoft Entwicklerwerkzeuge: Mehrere Schwachstellen
CVE-2026-100205 · CVE-2026-102229 · CVE-2026-102231 · CVE-2026-102232 · CVE-2026-102233 · CVE-2026-102234 · CVE-2026-102235 · CVE-2026-102238 · CVE-2026-102851 · CVE-2026-102869 · CVE-2026-102870 · CVE-2026-103572 · CVE-2026-105016 · CVE-2026-105729 · CVE-2026-105732 · CVE-2026-108398 · CVE-2026-109468 · CVE-2026-58280 · CVE-2026-66822 · CVE-2026-69370 · CVE-2026-69651 · CVE-2026-70007 · CVE-2026-70035 · CVE-2026-70098 · CVE-2026-70159 · CVE-2026-70161 · CVE-2026-70162 · CVE-2026-70165 · CVE-2026-70174 · CVE-2026-70175 · CVE-2026-70179 · CVE-2026-70181 · CVE-2026-70183 · CVE-2026-70186 · CVE-2026-70188 · CVE-2026-70190 · CVE-2026-70194 · CVE-2026-70196 · CVE-2026-70197 · CVE-2026-83520 · CVE-2026-84008 · CVE-2026-85363 · CVE-2026-85790 · CVE-2026-87697 · CVE-2026-88092 · CVE-2026-92707 · CVE-2026-96222 · CVE-2026-96224 · CVE-2026-96225 · CVE-2026-96229 · CVE-2026-96230 · CVE-2026-96231 · CVE-2026-96232 · CVE-2026-96233 · CVE-2026-96234 · CVE-2026-96235 · CVE-2026-96236 · CVE-2026-96237 · CVE-2026-96238 · CVE-2026-96251 · CVE-2026-96303 · CVE-2026-96957 · CVE-2026-96958 · CVE-2026-96959 · CVE-2026-96960 · CVE-2026-97788 · CVE-2026-97801
RHSA-2026:86195: Red Hat Security Advisory: .NET 10.0 security, bug fix, and enhancement update
CVE-2026-58280 · CVE-2026-66822 · CVE-2026-69651 · CVE-2026-70159 · CVE-2026-70175 · CVE-2026-70179 · CVE-2026-70181 · CVE-2026-70183 · CVE-2026-70186 · CVE-2026-70188 · CVE-2026-70196 · CVE-2026-84008 · CVE-2026-88092 · CVE-2026-92707 · CVE-2026-96225 · CVE-2026-96230 · CVE-2026-96231 · CVE-2026-96233 · CVE-2026-96236 · CVE-2026-96237 · CVE-2026-96238 · CVE-2026-96957 · CVE-2026-96958 · CVE-2026-96959 · CVE-2026-96960 · CVE-2026-102870
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Improper control of generation of code ('code injection') in ASP.NET Core allows an unauthorized attacker to execute code over a network.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Awaiting Analysis
Weakness classifications: CWE-94
published: 2026-10-13T19:17:51.617
lastModified: 2026-10-25T18:16:42.253
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
## 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 ## <a name="affected-packages"></a>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.Server](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.WebAssembly.Server) | >= 10.0.0, <= 10.0.13 | 10.0.14 [Microsoft.AspNetCore.Components.WebAssembly.Server](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.WebAssembly.Server) | >= 11.0.0-preview.1, < 11.0.0-rc.3.26522.148 | 11.0.0-rc.3.26522.148 ## Advisory FAQ ### <a name="how-affected"></a>How do I know if I am affected? You are affected if you use a vulnerable version of `Microsoft.AspNetCore.Components.WebAssembly.Server` to debug a Blazor WebAssembly application and evaluate an expression involving attacker-controlled application data. ### <a name="how-fix"></a>How do I fix the issue? 1. Install the latest supported version of .NET. 2. Update `Microsoft.AspNetCore.Components.WebAssembly.Server` to the patched version for the .NET release used by the application. Once the updated package or runtime is installed, restart the debugger and development environment. ## Other Information ### Reporting Security Issues If you have found a potential security issue in a supported version of .NET, please report it to the Microsoft Security Response Center (MSRC) via the [MSRC Researcher Portal](https://msrc.microsoft.com/report/vulnerability/new). Further information can be found in the MSRC [Report an Issue FAQ](https://www.microsoft.com/msrc/faqs-report-an-issue). Security reports made through MSRC may qualify for the Microsoft .NET Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty. ### Support You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repositories are located at https://github.com/dotnet/runtime and https://github.com/dotnet/aspnetcore. The Announcements repository (https://github.com/dotnet/announcements) will contain this bulletin as an issue and will include a link to a discussion issue. ### Disclaimer The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. ### External Links [CVE-2026-102870](https://www.cve.org/CVERecord?id=CVE-2026-102870) ### Acknowledgements alittleston3 ### Revisions V1.0 (10/13/2026): Advisory published. V1.1 (11/03/2026): Advisory updated with corrected .NET 10 and .NET 11 debugger packages and versions under the existing CVE.
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Publisher rating · HIGH