Is Microsoft.AspNetCore.Mvc.Core 2.0 vulnerable?

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

No known advisories in the last release

Microsoft.AspNetCore.Mvc.Core 2.0.4, the last 2.0 release, has no known advisories. 1 advisory affects earlier 2.0.x releases, so update to 2.0.4.

Update within 2.0:dotnet add package Microsoft.AspNetCore.Mvc.Core --version 2.0.4

Is your project on an affected Microsoft.AspNetCore.Mvc.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

Fixed within 2.0.x, affecting earlier releases

  • HighCVE-2017-11879GHSA-3wcj-rg8q-9cqv14 May 2022

    Open redirect in ASP.NET Core

    Affected
    >=2.0.0 <2.0.1
    Fixed in
    2.0.1

Every Microsoft.AspNetCore.Mvc.Core 2.0.x release

Affected: 2.0.0. 2.0.1 and later are not affected. Latest Microsoft.AspNetCore.Mvc.Core: 2.3.14.

VersionKnown advisories
Microsoft.AspNetCore.Mvc.Core 2.0.4None
Microsoft.AspNetCore.Mvc.Core 2.0.3None
Microsoft.AspNetCore.Mvc.Core 2.0.2None
Microsoft.AspNetCore.Mvc.Core 2.0.1None
Microsoft.AspNetCore.Mvc.Core 2.0.0CVE-2017-11879

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

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

Other Microsoft.AspNetCore.Mvc.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.