Is Microsoft.AspNetCore.App 2.2 vulnerable?
NuGet · 9 releases from 2.2.0 to 2.2.8 · latest Microsoft.AspNetCore.App is 2.2.8 · checked 18 Nov 2026
No known advisories in the last release
Microsoft.AspNetCore.App 2.2.8, the last 2.2 release, has no known advisories. 2 advisories affect earlier 2.2.x releases, so update to 2.2.8.
dotnet add package Microsoft.AspNetCore.App --version 2.2.8Is your project on an affected Microsoft.AspNetCore.App?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 2.2.x, affecting earlier releases
Open redirect in ASP.NET Core
- Affected
- >=2.2.0 <2.2.6 · >=2.1.0 <2.1.12
- Fixed in
- 2.1.12, 2.2.6
Denial of service in ASP.NET Core
- Affected
- >=2.2.0 <2.2.1 · >=2.1.0 <2.1.7
- Fixed in
- 2.1.7, 2.2.1
Every Microsoft.AspNetCore.App 2.2.x release
Affected: 2.2.0 to 2.2.5. 2.2.6 and later are not affected.
| Version | Known advisories |
|---|---|
| Microsoft.AspNetCore.App 2.2.8 | None |
| Microsoft.AspNetCore.App 2.2.7 | None |
| Microsoft.AspNetCore.App 2.2.6 | None |
| Microsoft.AspNetCore.App 2.2.5 | CVE-2019-1075 |
| Microsoft.AspNetCore.App 2.2.4 | CVE-2019-1075 |
| Microsoft.AspNetCore.App 2.2.3 | CVE-2019-1075 |
| Microsoft.AspNetCore.App 2.2.2 | CVE-2019-1075 |
| Microsoft.AspNetCore.App 2.2.1 | CVE-2019-1075 |
| Microsoft.AspNetCore.App 2.2.0 | CVE-2019-1075, CVE-2019-0564 |
Which of your client projects are still on Microsoft.AspNetCore.App 2.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact Microsoft.AspNetCore.App version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other Microsoft.AspNetCore.App 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.