# CVE-2026-57099: ASP.NET Core Denial of Service Vulnerability

> An unauthorized attacker can cause a denial of service in ASP.NET Core OData by exploiting resource allocation limits.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-7whw-q9mg-h337

## What is CVE-2026-57099?

CVE-2026-57099 is a high-severity denial of service vulnerability in Microsoft AspNetCore.OData, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Allocation of resources without limits or throttling in ASP.NET Core allows an unauthorized attacker to deny service over a network.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Microsoft Asp.net Core Odata.

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

No fix has been published for CVE-2026-57099 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-57099 being exploited?

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

## Other vulnerabilities in Microsoft AspNetCore.OData

- [CVE-2026-45646](https://insights.sbomify.com/CVE-2026-45646/): OData for ASP.NET and ASP.NET Core Denial of Service Vulnerability (high 7.5)
- [CVE-2026-50506](https://insights.sbomify.com/CVE-2026-50506/): OData for ASP.NET and ASP.NET Core Denial of Service Vulnerability (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57099 is a high-severity denial of service vulnerability in Microsoft AspNetCore.OData, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-57099 in the wild and no public exploit code.

Affected product: Microsoft AspNetCore.OData. 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-57099/ (Markdown: https://insights.sbomify.com/CVE-2026-57099/index.md)
```

## Sources

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

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