Is Microsoft.AspNetCore.Server.Kestrel.Core 2.0 vulnerable?

NuGet · 5 releases from 2.0.0 to 2.0.4 · latest Microsoft.AspNetCore.Server.Kestrel.Core is 2.3.14 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. Microsoft.AspNetCore.Server.Kestrel.Core 2.0.4, the last 2.0 release, is affected by 2 known security advisories (1 critical, 1 high), including CVE-2025-55315, CVE-2021-1723. 3 more affect earlier 2.0.x releases. Upgrade to 2.3.6 or later to fix all of them.

Upgrade with:dotnet add package Microsoft.AspNetCore.Server.Kestrel.Core --version 2.3.6

Is your project on an affected Microsoft.AspNetCore.Server.Kestrel.Core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting Microsoft.AspNetCore.Server.Kestrel.Core 2.0.4

  • CriticalCVE-2025-55315GHSA-5rrx-jjjq-q2r514 Oct 2025

    Microsoft Security Advisory CVE-2025-55315: .NET Security Feature Bypass Vulnerability

    Affected
    <2.3.6
    Fixed in
    2.3.6
  • HighCVE-2021-1723GHSA-242j-2gm6-5rwx24 May 2022

    ASP.NET Core and Visual Studio Denial of Service Vulnerability

    Affected
    <2.1.25
    Fixed in
    2.1.25

Fixed within 2.0.x, affecting earlier releases

  • MediumGHSA-cgpw-2gph-2r9g16 Oct 2018

    Moderate severity vulnerability that affects Microsoft.AspNetCore.All, Microsoft.AspNetCore.App, and Microsoft.AspNetCore.Server.Kestrel.Core

    Affected
    >=2.0.0 <2.0.4 · >=2.1.0 <2.1.2
    Fixed in
    2.0.4, 2.1.2
  • MediumGHSA-3m2r-q8x3-xmf716 Oct 2018

    Moderate severity vulnerability that affects Microsoft.AspNetCore.All, Microsoft.AspNetCore.Server.Kestrel.Core, Microsoft.AspNetCore.Server.Kestrel.Transport.Abstractions, and Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv

    Affected
    >=2.0.0 <2.0.3
    Fixed in
    2.0.3
  • HighCVE-2018-0787GHSA-365p-96qv-xr7g16 Oct 2018

    ASP.NET Core allow an elevation of privilege

    Affected
    >=2.0.0 <2.0.2
    Fixed in
    2.0.2

Every Microsoft.AspNetCore.Server.Kestrel.Core 2.0.x release

Affected: 2.0.0 to 2.0.4. Latest Microsoft.AspNetCore.Server.Kestrel.Core: 2.3.14.

VersionKnown advisories
Microsoft.AspNetCore.Server.Kestrel.Core 2.0.4CVE-2025-55315, CVE-2021-1723
Microsoft.AspNetCore.Server.Kestrel.Core 2.0.3CVE-2025-55315, CVE-2021-1723, GHSA-cgpw-2gph-2r9g
Microsoft.AspNetCore.Server.Kestrel.Core 2.0.2CVE-2025-55315, CVE-2021-1723, GHSA-cgpw-2gph-2r9g, GHSA-3m2r-q8x3-xmf7
Microsoft.AspNetCore.Server.Kestrel.Core 2.0.1CVE-2025-55315, CVE-2021-1723, GHSA-cgpw-2gph-2r9g, GHSA-3m2r-q8x3-xmf7, CVE-2018-0787
Microsoft.AspNetCore.Server.Kestrel.Core 2.0.0CVE-2025-55315, CVE-2021-1723, GHSA-cgpw-2gph-2r9g, GHSA-3m2r-q8x3-xmf7, CVE-2018-0787

Which of your client projects are still on Microsoft.AspNetCore.Server.Kestrel.Core 2.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact Microsoft.AspNetCore.Server.Kestrel.Core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other Microsoft.AspNetCore.Server.Kestrel.Core 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.