CefSharp.WinForms vulnerabilities

The CefSharp Chromium-based browser component (WinForms control).

Registry
NuGet
Latest
156.0.300

6 known advisories

The latest version, 156.0.300, is not affected by any of them. Projects on older versions may be.

Update to the latest version:dotnet add package CefSharp.WinForms --version 156.0.300

Is your project on an affected CefSharp.WinForms?

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

Security advisories for CefSharp.WinForms

  • HighGHSA-f87w-3j5w-v58p12 Apr 2025

    CefSharp affected by incorrect handle provided in unspecified circumstances in Mojo on Windows

    Affected
    <134.3.90
    Fixed in
    134.3.90
  • HighCVE-2022-0609GHSA-vv6j-ww6x-54gx22 Feb 2022

    Use after free in Animation

    Affected
    <98.1.210
    Fixed in
    98.1.210
  • HighCVE-2020-16009GHSA-m7mf-48hp-5qmr2 Dec 2020

    Inappropriate implementation in V8

    Affected
    <86.0.241
    Fixed in
    86.0.241
  • HighCVE-2020-16017GHSA-gvqv-779r-4jgp27 Nov 2020

    Use after free in CefSharp

    Affected
    <86.0.241
    Fixed in
    86.0.241
  • HighCVE-2020-16013GHSA-x7fx-mcc9-27j727 Nov 2020

    Inappropriate implementation in V8 in CefSharp

    Affected
    <86.0.241
    Fixed in
    86.0.241
  • MediumCVE-2020-15999GHSA-pv36-h7jh-qm6227 Oct 2020

    Heap buffer overflow in CefSharp

    Affected
    <85.3.130
    Fixed in
    85.3.130

Is your CefSharp.WinForms version vulnerable?

Which of your client projects still run an old CefSharp.WinForms?

NPMscan reads the packages.lock.json and .csproj files in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other NuGet packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the NuGet registry.