# CVE-2026-96237: .NET Remote Code Execution Vulnerability

> An unauthorized attacker can execute arbitrary code over the network due to inclusion of functionality from an untrusted control sphere in .NET.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/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:** UBUNTU-CVE-2026-96237

## What is CVE-2026-96237?

CVE-2026-96237 is a high-severity code injection vulnerability in Microsoft .NET 10.0 runtime, 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

Inclusion of functionality from untrusted control sphere in .NET allows an unauthorized attacker to execute code over a network.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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


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

Apply the vendor's patch.

## Is CVE-2026-96237 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96237 is a high-severity code injection vulnerability in Microsoft .NET 10.0 runtime, 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-96237 in the wild and no public exploit code.

Affected product: Microsoft .NET 10.0 runtime. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-96237/ (Markdown: https://insights.sbomify.com/CVE-2026-96237/index.md)
```

## Sources

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

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