Is Microsoft.AspNetCore.Http 1.0 vulnerable?
NuGet · 5 releases from 1.0.0 to 1.0.4 · latest Microsoft.AspNetCore.Http is 2.3.14 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. Microsoft.AspNetCore.Http 1.0.4, the last 1.0 release, is affected by 1 known security advisory (1 high), including CVE-2020-1045. Upgrade to 2.1.22 or later to fix all of them.
dotnet add package Microsoft.AspNetCore.Http --version 2.1.22Is your project on an affected Microsoft.AspNetCore.Http?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting Microsoft.AspNetCore.Http 1.0.4
Cookie parsing failure
- Affected
- <2.1.22
- Fixed in
- 2.1.22
Every Microsoft.AspNetCore.Http 1.0.x release
Affected: 1.0.0 to 1.0.4. Latest Microsoft.AspNetCore.Http: 2.3.14.
| Version | Known advisories |
|---|---|
| Microsoft.AspNetCore.Http 1.0.4 | CVE-2020-1045 |
| Microsoft.AspNetCore.Http 1.0.3 | CVE-2020-1045 |
| Microsoft.AspNetCore.Http 1.0.2 | CVE-2020-1045 |
| Microsoft.AspNetCore.Http 1.0.1 | CVE-2020-1045 |
| Microsoft.AspNetCore.Http 1.0.0 | CVE-2020-1045 |
Which of your client projects are still on Microsoft.AspNetCore.Http 1.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact Microsoft.AspNetCore.Http version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other Microsoft.AspNetCore.Http 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.