Is CefSharp.Wpf.NETCore 126.2 vulnerable?
NuGet · 2 releases from 126.2.70 to 126.2.180 · latest CefSharp.Wpf.NETCore is 156.0.300 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. CefSharp.Wpf.NETCore 126.2.180, the last 126.2 release, is affected by 1 known security advisory (1 high). Upgrade to 134.3.90 or later to fix all of them.
dotnet add package CefSharp.Wpf.NETCore --version 134.3.90Is your project on an affected CefSharp.Wpf.NETCore?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting CefSharp.Wpf.NETCore 126.2.180
CefSharp affected by incorrect handle provided in unspecified circumstances in Mojo on Windows
- Affected
- <134.3.90
- Fixed in
- 134.3.90
Every CefSharp.Wpf.NETCore 126.2.x release
Affected: 126.2.70 to 126.2.180. Latest CefSharp.Wpf.NETCore: 156.0.300.
| Version | Known advisories |
|---|---|
| CefSharp.Wpf.NETCore 126.2.180 | GHSA-f87w-3j5w-v58p |
| CefSharp.Wpf.NETCore 126.2.70 | GHSA-f87w-3j5w-v58p |
Which of your client projects are still on CefSharp.Wpf.NETCore 126.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact CefSharp.Wpf.NETCore version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other CefSharp.Wpf.NETCore 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.