# CVE-2025-26682: ASP.NET Core and Visual Studio Denial of Service Vulnerability

> An unauthorized attacker can cause a denial of service in ASP.NET Core 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:** Yes
- **Published:** 8 Apr 2025
- **Updated:** 10 Aug 2026
- **Also known as:** BELL-CVE-2025-26682, BIT-aspnet-core-2025-26682, GHSA-gf2r-7cq8-xww9, UBUNTU-CVE-2025-26682, USN-7427-1

## What is CVE-2025-26682?

CVE-2025-26682 is a high-severity denial of service vulnerability in Microsoft Visual Studio 2022, published on 8 Apr 2025. 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-2025-26682?

1 open source package ship an affected version, including aspnet-core. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aspnet-core` | Bitnami | From 8.0.0 | 8.0.15, 9.0.4 |

Products: Microsoft Asp.net Core, Microsoft Visual Studio 2022.

## How do I fix CVE-2025-26682?

Upgrade aspnet-core to a fixed version for your release line: 8.0.15 or 9.0.4.

## Is CVE-2025-26682 being exploited?

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

## Other vulnerabilities in Microsoft Visual Studio 2022

- [CVE-2025-55315](https://insights.sbomify.com/CVE-2025-55315/): ASP.NET Security Feature Bypass Vulnerability (critical 9.9)
- [CVE-2026-88092](https://insights.sbomify.com/CVE-2026-88092/): ASP.NET Core Tampering Vulnerability (critical 9.4)
- [CVE-2026-40372](https://insights.sbomify.com/CVE-2026-40372/): ASP.NET Core Elevation of Privilege Vulnerability (critical 9.1)
- [CVE-2021-43877](https://insights.sbomify.com/CVE-2021-43877/): ASP.NET Core and Visual Studio Elevation of Privilege Vulnerability (high 8.8)
- [CVE-2020-0603](https://insights.sbomify.com/CVE-2020-0603/): Remote code execution in ASP.NET Core (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-26682 and fix it if it is affected.

What it is: CVE-2025-26682 is a high-severity denial of service vulnerability in Microsoft Visual Studio 2022, published on 8 Apr 2025. 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-2025-26682 in the wild and no public exploit code.

Affected packages and fixed versions:
- aspnet-core (Bitnami): affected from 8.0.0; fixed in 8.0.15, 9.0.4

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

## Sources

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

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