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