# CVE-2026-25667: Denial of service in n/a

> Remote attackers can cause excessive CPU consumption in ASP.NET Core Kestrel via crafted QUIC packets, leading to denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Mar 2026
- **Updated:** 29 Apr 2026
- **Also known as:** BIT-dotnet-2026-25667, BIT-dotnet-sdk-2026-25667, GHSA-jc8w-j2q2-vwjx, MINI-4xj4-jqfh-j879, MINI-9mr2-2hf7-crmq

## What is CVE-2026-25667?

CVE-2026-25667 is a high-severity denial of service vulnerability in Microsoft .Net, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ASP.NET Core Kestrel in Microsoft .NET 8.0 before 8.0.22 and .NET 9.0 before 9.0.11 allows a remote attacker to cause excessive CPU consumption by sending a crafted QUIC packet, because of an incorrect exit condition for HTTP/3 Encoder/Decoder stream processing.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

2 open source packages ship an affected version, including dotnet and dotnet-sdk. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dotnet` | Bitnami | From 8.0.0 | 8.0.22, 9.0.11 |
| `dotnet-sdk` | Bitnami | From 8.0.0 | 8.0.22, 9.0.11 |

Products: Microsoft .Net.

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

Upgrade dotnet to a fixed version for your release line: 8.0.22 or 9.0.11.

## Is CVE-2026-25667 being exploited?

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

## Other vulnerabilities in Microsoft .Net

- [CVE-2024-43498](https://insights.sbomify.com/CVE-2024-43498/): .NET and Visual Studio Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2024-0057](https://insights.sbomify.com/CVE-2024-0057/): NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability (critical 9.1)
- [CVE-2026-96957](https://insights.sbomify.com/CVE-2026-96957/): .NET Security Feature Bypass Vulnerability (high 8.8)
- [CVE-2026-69439](https://insights.sbomify.com/CVE-2026-69439/): .NET and Visual Studio Elevation of Privilege Vulnerability (high 8.8)
- [CVE-2026-71328](https://insights.sbomify.com/CVE-2026-71328/): .NET and Visual Studio Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25667 is a high-severity denial of service vulnerability in Microsoft .Net, published on 19 Mar 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-25667 in the wild and no public exploit code.

Affected packages and fixed versions:
- dotnet (Bitnami): affected from 8.0.0; fixed in 8.0.22, 9.0.11
- dotnet-sdk (Bitnami): affected from 8.0.0; fixed in 8.0.22, 9.0.11

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

## Sources

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

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