Is Microsoft.AspNetCore.Http.Connections 1.2 vulnerable?
NuGet · 8 releases from 1.2.0 to 1.2.14 · latest Microsoft.AspNetCore.Http.Connections is 1.2.14 · checked 18 Nov 2026
No known advisories in the last release
Microsoft.AspNetCore.Http.Connections 1.2.14, the last 1.2 release, has no known advisories. 1 advisory affects earlier 1.2.x releases, so update to 1.2.14.
dotnet add package Microsoft.AspNetCore.Http.Connections --version 1.2.14Is your project on an affected Microsoft.AspNetCore.Http.Connections?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 1.2.x, affecting earlier releases
Microsoft Security Advisory CVE-2026-114146 - ASP.NET Core Elevation of Privilege Vulnerability
- Affected
- >=1.2.0 <1.2.14
- Fixed in
- 1.2.14
Every Microsoft.AspNetCore.Http.Connections 1.2.x release
Affected: 1.2.0 to 1.2.13. 1.2.14 is not affected.
| Version | Known advisories |
|---|---|
| Microsoft.AspNetCore.Http.Connections 1.2.14 | None |
| Microsoft.AspNetCore.Http.Connections 1.2.13 | CVE-2026-114146 |
| Microsoft.AspNetCore.Http.Connections 1.2.12 | CVE-2026-114146 |
| Microsoft.AspNetCore.Http.Connections 1.2.11 | CVE-2026-114146 |
| Microsoft.AspNetCore.Http.Connections 1.2.10 | CVE-2026-114146 |
| Microsoft.AspNetCore.Http.Connections 1.2.9 | CVE-2026-114146 |
| Microsoft.AspNetCore.Http.Connections 1.2.8 | CVE-2026-114146 |
| Microsoft.AspNetCore.Http.Connections 1.2.0 | CVE-2026-114146 |
Which of your client projects are still on Microsoft.AspNetCore.Http.Connections 1.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact Microsoft.AspNetCore.Http.Connections version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other Microsoft.AspNetCore.Http.Connections 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.