Is Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets 2.1 vulnerable?
NuGet · 5 releases from 2.1.0 to 2.1.40 · latest Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets is 2.3.14 · checked 18 Nov 2026
No known advisories in the last release
Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets 2.1.40, the last 2.1 release, has no known advisories. 1 advisory affects earlier 2.1.x releases, so update to 2.1.40.
dotnet add package Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets --version 2.1.40Is your project on an affected Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 2.1.x, affecting earlier releases
.NET Denial of Service Vulnerability
- Affected
- <2.1.40
- Fixed in
- 2.1.40
Every Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets 2.1.x release
Affected: 2.1.0 to 2.1.3. 2.1.40 is not affected. Latest Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets: 2.3.14.
| Version | Known advisories |
|---|---|
| Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets 2.1.40 | None |
| Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets 2.1.3 | CVE-2023-38180 |
| Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets 2.1.2 | CVE-2023-38180 |
| Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets 2.1.1 | CVE-2023-38180 |
| Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets 2.1.0 | CVE-2023-38180 |
Which of your client projects are still on Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets 2.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.