Is CefSharp.Common 144.0 vulnerable?

NuGet · 5 releases from 144.0.120 to 144.0.300 · latest CefSharp.Common is 156.0.300 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. CefSharp.Common 144.0.300, the last 144.0 release, is affected by 1 known security advisory (1 medium), including CVE-2026-48796. Upgrade to 148.0.90 or later to fix all of them.

Upgrade with:dotnet add package CefSharp.Common --version 148.0.90

Is your project on an affected CefSharp.Common?

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

Advisories affecting CefSharp.Common 144.0.300

  • MediumCVE-2026-48796GHSA-85jm-cwp2-mvpv30 Jun 2026

    CefSharp.Common: `FolderSchemeHandlerFactory` path boundary check can expose files outside the configured root folder

    Affected
    <148.0.90
    Fixed in
    148.0.90

Every CefSharp.Common 144.0.x release

Affected: 144.0.120 to 144.0.300. Latest CefSharp.Common: 156.0.300.

VersionKnown advisories
CefSharp.Common 144.0.300CVE-2026-48796
CefSharp.Common 144.0.270CVE-2026-48796
CefSharp.Common 144.0.260CVE-2026-48796
CefSharp.Common 144.0.250CVE-2026-48796
CefSharp.Common 144.0.120CVE-2026-48796

Which of your client projects are still on CefSharp.Common 144.0?

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

Other CefSharp.Common 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.