How severe is CVE-2023-38180?

CVE-2023-38180 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-38180?

CVE-2023-38180 affects the following packages: Microsoft.AspNetCore.App.Runtime.win-arm64 (NuGet), Microsoft.AspNetCore.App.Runtime.win-x64 (NuGet), Microsoft.AspNetCore.App.Runtime.win-x86 (NuGet), Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv (NuGet), Microsoft.AspNetCore.App.Runtime.win-arm64 (NuGet), Microsoft.AspNetCore.App.Runtime.win-x64 (NuGet), Microsoft.AspNetCore.App.Runtime.win-x86 (NuGet), Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv (NuGet), and 1 more. Ecosystems affected: NuGet.

How do I fix CVE-2023-38180?

Update Microsoft.AspNetCore.App.Runtime.win-arm64 to version 7.0.10 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is CVE-2023-38180 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2023-38180, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-38180?

CVE-2023-38180 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 76th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2023-38180 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2023-38180 (Microsoft .NET Core and Visual Studio Denial-of-Service Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-08-09. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-08-30. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

When was CVE-2023-38180 published, and has it been updated?

CVE-2023-38180 was published on August 8, 2023 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2023-08-09 — agencies required to remediate by 2023-08-30

.NET NuGet

CVE-2023-38180

HIGH

.NET Denial of Service Vulnerability

Also known asBIT-aspnet-core-2023-38180BIT-dotnet-2023-38180BIT-dotnet-sdk-2023-38180GHSA-vmch-3w2x-vhgq

Published

Aug 8, 2023

Updated

Apr 10, 2026

Affected

9 pkgs

Patched

9 / 9

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk76th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

9 pkgs affected

.NETMicrosoft.AspNetCore.App.Runtime.win-arm64.NETMicrosoft.AspNetCore.App.Runtime.win-x64.NETMicrosoft.AspNetCore.App.Runtime.win-x86.NETMicrosoft.AspNetCore.Server.Kestrel.Transport.Libuv.NETMicrosoft.AspNetCore.App.Runtime.win-arm64.NETMicrosoft.AspNetCore.App.Runtime.win-x64.NETMicrosoft.AspNetCore.App.Runtime.win-x86.NETMicrosoft.AspNetCore.Server.Kestrel.Transport.Libuv+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

.NET and Visual Studio Denial of Service Vulnerability

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Microsoft.AspNetCore.App.Runtime.win-arm64`	≥ 7.0.0&&< 7.0.10	7.0.10
.NETNuGet	`Microsoft.AspNetCore.App.Runtime.win-x64`	≥ 7.0.0&&< 7.0.10	7.0.10
.NETNuGet	`Microsoft.AspNetCore.App.Runtime.win-x86`	≥ 7.0.0&&< 7.0.10	7.0.10
.NETNuGet	`Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv`	≥ 6.0.0&&< 6.0.21	6.0.21
.NETNuGet	`Microsoft.AspNetCore.App.Runtime.win-arm64`	≥ 6.0.0&&< 6.0.21	6.0.21
.NETNuGet	`Microsoft.AspNetCore.App.Runtime.win-x64`	≥ 6.0.0&&< 6.0.21	6.0.21

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

.NET and Visual Studio Denial of Service Vulnerability

portal.msrc.microsoft.comMSAug 2023

.NET and Visual Studio Denial of Service Vulnerability

cisa.govCISAAug 2023

Frequently Asked Questions

.NET and Visual Studio Denial of Service Vulnerability

O3 Security · Impact-Aware SCA

Is CVE-2023-38180 in your stack?

O3 detects CVE-2023-38180 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works