.NET Denial of Service Vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2023-38178: 2.59% estimated exploitation activity in the next 30 days; percentile 85.31 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Microsoft Security Advisory CVE-2023-38178: .NET Denial of Service Vulnerability <a name="executive-summary"</aExecutive summary Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exists in .NET Kestrel where a malicious client can bypass QUIC stream limit in HTTP/3 in both ASP.NET and .NET runtimes resulting in denial of service. Announcement Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/268 <a name="mitigation-factors"</aMitigation factors Microsoft has not identified any mitigating factors for this vulnerability. <a name="affected-software"</aAffected software Any .NET 7.0 application running on .NET 7.0.9 or earlier. If your application uses the following package versions, ensure you update to the latest version of .NET. <a name=".NET 7"</a.NET 7…

Published by the source

9 Aug 2023, 13:04 UTC

Last modified by the source

3 Jun 2024, 18:31 UTC

Source last checked

26 Oct 2026, 17:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-p57v-gv7q-4xfm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-38178

Advisory: .NET Denial of Service Vulnerability
IDs: CVE-2023-38178, GHSA-p57v-gv7q-4xfm
Record: https://patchnext.com/advisories/cve-2023-38178 (revision 1, source checked 26 Oct 2026, 17:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: microsoft.netcore.app.runtime.win-x86 7.0.10; microsoft.netcore.app.runtime.win-arm64 7.0.10; microsoft.aspnetcore.app.runtime.win-x86 7.0.10; microsoft.aspnetcore.app.runtime.win-arm 7.0.10; microsoft.aspnetcore.app.runtime.win-x64 7.0.10; microsoft.netcore.app.runtime.win-arm 7.0.10; microsoft.aspnetcore.app.runtime.win-arm64 7.0.10; microsoft.netcore.app.runtime.win-x64 7.0.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet microsoft.netcore.app.runtime.win-x86: affected >= 7.0.0, <= 7.0.9; fixed in 7.0.10
- NuGet microsoft.netcore.app.runtime.win-arm64: affected >= 7.0.0, <= 7.0.9; fixed in 7.0.10
- NuGet microsoft.aspnetcore.app.runtime.win-x86: affected >= 7.0.0, <= 7.0.9; fixed in 7.0.10
- NuGet microsoft.aspnetcore.app.runtime.win-arm: affected >= 7.0.0, <= 7.0.9; fixed in 7.0.10
- NuGet microsoft.aspnetcore.app.runtime.win-x64: affected >= 7.0.0, <= 7.0.9; fixed in 7.0.10
- NuGet microsoft.netcore.app.runtime.win-arm: affected >= 7.0.0, <= 7.0.9; fixed in 7.0.10
- NuGet microsoft.aspnetcore.app.runtime.win-arm64: affected >= 7.0.0, <= 7.0.9; fixed in 7.0.10
- NuGet microsoft.netcore.app.runtime.win-x64: affected >= 7.0.0, <= 7.0.9; fixed in 7.0.10

## Suggested inspection (read-only)
- NuGet microsoft.netcore.app.runtime.win-x86: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.win-arm64: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.app.runtime.win-x86: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.app.runtime.win-arm: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.app.runtime.win-x64: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.win-arm: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.app.runtime.win-arm64: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.win-x64: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on microsoft.netcore.app.runtime.win-x86, microsoft.netcore.app.runtime.win-arm64, microsoft.aspnetcore.app.runtime.win-x86, microsoft.aspnetcore.app.runtime.win-arm, microsoft.aspnetcore.app.runtime.win-x64, microsoft.netcore.app.runtime.win-arm, microsoft.aspnetcore.app.runtime.win-arm64, microsoft.netcore.app.runtime.win-x64.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p57v-gv7q-4xfm (GitHub-reviewed advisory GHSA-p57v-gv7q-4xfm lists affected ranges: NuGet microsoft.aspnetcore.app.runtime.win-arm64 >=7.0.0 =7.0.0 =7.0.0 =7.0.0 =7.0.0 =7.0.0 <=7.0.9; NuGet microsoft.netcore.app.runtime.win-x64…)

Commands are suggestions: review each one before running it.