Microsoft Security Advisory CVE-2026-96230 - ASP.NET Core Remote Code Execution Vulnerability
CVE-2026-96230 · GHSA-qjpx-jqm5-h2c4 · published 13 Oct 2026
How serious is it
- Severity: high, CVSS score 8.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-96230?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
Microsoft.AspNetCore.Components.WebAssembly.Server(NuGet) >= 10.0.0, <= 10.0.12Microsoft.AspNetCore.Components.WebAssembly.Server(NuGet) >= 11.0.0-preview.1, <= 11.0.0-rc.1Microsoft.AspNetCore.Components.WebAssembly.Server(NuGet) >= 8.0.0, <= 8.0.31Microsoft.AspNetCore.Components.WebAssembly.Server(NuGet) >= 9.0.0, <= 9.0.20
How to check
- Look for
Microsoft.AspNetCore.Components.WebAssembly.Serverin your lockfile and compare its version with the range above. - Or paste your lockfile into the checker: it lists every package with a known vulnerability, this one included.
How to fix
Copies a prompt for Claude Code, Cursor or Codex: it checks your lockfiles for this and upgrades it.
- On >= 10.0.0, <= 10.0.12: Upgrade
Microsoft.AspNetCore.Components.WebAssembly.Serverto 10.0.13 or later, commit the lockfile and redeploy. - On >= 11.0.0-preview.1, <= 11.0.0-rc.1: Upgrade
Microsoft.AspNetCore.Components.WebAssembly.Serverto 11.0.0-rc.2 or later, commit the lockfile and redeploy. - On >= 8.0.0, <= 8.0.31: Upgrade
Microsoft.AspNetCore.Components.WebAssembly.Serverto 8.0.32 or later, commit the lockfile and redeploy. - On >= 9.0.0, <= 9.0.20: Upgrade
Microsoft.AspNetCore.Components.WebAssembly.Serverto 9.0.21 or later, commit the lockfile and redeploy. - If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
## Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability 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 development-server debug page can reflect unencoded exception text, allowing cross-origin script injection through the unauthenticated `/_framework/debug` endpoint used by `dotnet watch`.
## Announcement
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/478
## 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-79 (Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'))
## 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.12 | 10.0.13
[Microsoft.AspNetCore.Components.WebAssembly.Server](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.WebAssembly.Server) | >= 11.0.0-preview.1, <= 11.0.0-rc.1 | 11.0.0-rc.2
[Microsoft.AspNetCore.Components.WebAssembly.Server](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.WebAssembly.Server) | >= 8.0.0, <= 8.0.31 | 8.0.32
[Microsoft.AspNetCore.Components.WebAssembly.Server](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.WebAssembly.Server) | >= 9.0.0, <= 9.0.20 | 9.0.21
## Advisory FAQ
### <a name="how-affected"></a>How do I know if I am affected?
If using a package listed in [affected packages](#affected-packages), you're exposed to the vulnerability.
### <a name="how-fix"></a>How do I fix the issue?
1. To fix the issue please install the latest version of .NET. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs.
2. If your application references the vulnerable package, update the package reference to the patched version. You can list the versions you have installed by running the `dotnet --info` command.
Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.
Additionally, if you've deployed [self-contained applications](https://docs.microsoft.com/dotnet/core/deploying/#self-contained-deployments-scd) targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.
## 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 repos are located at https://github.com/dotnet/runtime. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked 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-96230](https://www.cve.org/CVERecord?id=CVE-2026-96230)
### Acknowledgements
- Kevin Gosse
### Revisions
V1.0 (10/13/2026): Advisory published.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- github.com/dotnet/aspnetcore/security/advisories/GHSA-qjpx-jqm5-h2c4
- github.com/dotnet/announcements/issues/478
- github.com/dotnet/aspnetcore/discussions/69802
- nvd.nist.gov/vuln/detail/CVE-2026-96230
- msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96230
- github.com/advisories/GHSA-qjpx-jqm5-h2c4
- github.com/dotnet/aspnetcore
Merged from GitHub Advisory Database, CVE List, OSV. Last updated 23 Oct 2026. All vulnerabilities · RSS · JSON