Is Microsoft.AspNetCore.Server.HttpSys 2.1 vulnerable?

NuGet · 3 releases from 2.1.0 to 2.1.12 · latest Microsoft.AspNetCore.Server.HttpSys is 2.3.14 · checked 18 Nov 2026

No known advisories in the last release

Microsoft.AspNetCore.Server.HttpSys 2.1.12, the last 2.1 release, has no known advisories. 1 advisory affects earlier 2.1.x releases, so update to 2.1.12.

Update within 2.1:dotnet add package Microsoft.AspNetCore.Server.HttpSys --version 2.1.12

Is your project on an affected Microsoft.AspNetCore.Server.HttpSys?

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.1.x, affecting earlier releases

  • MediumCVE-2019-1075GHSA-prrf-397v-83xh24 May 2022

    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

Every Microsoft.AspNetCore.Server.HttpSys 2.1.x release

Affected: 2.1.0 to 2.1.1. 2.1.12 is not affected. Latest Microsoft.AspNetCore.Server.HttpSys: 2.3.14.

VersionKnown advisories
Microsoft.AspNetCore.Server.HttpSys 2.1.12None
Microsoft.AspNetCore.Server.HttpSys 2.1.1CVE-2019-1075
Microsoft.AspNetCore.Server.HttpSys 2.1.0CVE-2019-1075

Which of your client projects are still on Microsoft.AspNetCore.Server.HttpSys 2.1?

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

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