# CVE-2026-96230: ASP.NET Core Remote Code Execution Vulnerability

> An attacker can execute code over the network via cross-site scripting in ASP.NET Core, requiring immediate patching for developers and administrators.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-qjpx-jqm5-h2c4, UBUNTU-CVE-2026-96230

## What is CVE-2026-96230?

CVE-2026-96230 is a high-severity cross-site scripting vulnerability in Microsoft Visual Studio 2022 version 17.14, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Improper neutralization of input during web page generation ('cross-site scripting') in ASP.NET Core allows an unauthorized attacker to execute code over a network.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-96230?

8 open source packages ship an affected version, including Microsoft.AspNetCore.Components.WebAssembly.Server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Microsoft.AspNetCore.Components.WebAssembly.Server` | NuGet | From 10.0.0 | 10.0.13 |
| `Microsoft.AspNetCore.Components.WebAssembly.Server` | NuGet | From 10.0.0 | 10.0.13 |
| `Microsoft.AspNetCore.Components.WebAssembly.Server` | NuGet | From 11.0.0-preview.1 | 11.0.0-rc.2 |
| `Microsoft.AspNetCore.Components.WebAssembly.Server` | NuGet | From 11.0.0-preview.1 | 11.0.0-rc.2 |
| `Microsoft.AspNetCore.Components.WebAssembly.Server` | NuGet | From 8.0.0 | 8.0.32 |
| `Microsoft.AspNetCore.Components.WebAssembly.Server` | NuGet | From 8.0.0 | 8.0.32 |
| `Microsoft.AspNetCore.Components.WebAssembly.Server` | NuGet | From 9.0.0 | 9.0.21 |
| `Microsoft.AspNetCore.Components.WebAssembly.Server` | NuGet | From 9.0.0 | 9.0.21 |

## How do I fix CVE-2026-96230?

Upgrade Microsoft.AspNetCore.Components.WebAssembly.Server to a fixed version for your release line: 10.0.13, 11.0.0-rc.2, 8.0.32 or 9.0.21.

## Is CVE-2026-96230 being exploited?

There is no known exploitation of CVE-2026-96230 in the wild and no public exploit code.

Public exploit code:

- Autonomous submission for "Microsoft Security Advisory CVE-2026-96230 - ASP.NET Core Remote Code Execution Vulnerability" (MSRC / GitHub Security Advisory) (github_poc): https://github.com/codevalai/microsoft-security-advisory-cv

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-96230 and fix it if it is affected.

What it is: CVE-2026-96230 is a high-severity cross-site scripting vulnerability in Microsoft Visual Studio 2022 version 17.14, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-96230 in the wild and no public exploit code.

Affected packages and fixed versions:
- Microsoft.AspNetCore.Components.WebAssembly.Server (NuGet): affected from 10.0.0; fixed in 10.0.13
- Microsoft.AspNetCore.Components.WebAssembly.Server (NuGet): affected from 10.0.0; fixed in 10.0.13
- Microsoft.AspNetCore.Components.WebAssembly.Server (NuGet): affected from 11.0.0-preview.1; fixed in 11.0.0-rc.2
- Microsoft.AspNetCore.Components.WebAssembly.Server (NuGet): affected from 11.0.0-preview.1; fixed in 11.0.0-rc.2
- Microsoft.AspNetCore.Components.WebAssembly.Server (NuGet): affected from 8.0.0; fixed in 8.0.32
- Microsoft.AspNetCore.Components.WebAssembly.Server (NuGet): affected from 8.0.0; fixed in 8.0.32
- Microsoft.AspNetCore.Components.WebAssembly.Server (NuGet): affected from 9.0.0; fixed in 9.0.21
- Microsoft.AspNetCore.Components.WebAssembly.Server (NuGet): affected from 9.0.0; fixed in 9.0.21

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-96230/ (Markdown: https://insights.sbomify.com/CVE-2026-96230/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-96230
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-96230
- OSV: https://osv.dev/vulnerability/CVE-2026-96230

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-96230/
Summaries are generated and may contain mistakes; the official description above is the record.