Vulnerabilities in pkg:nuget/CefSharp.Common

PACKAGE
Advisory Identifier: GHSA-85jm-cwp2-mvpv
Advisory Summary

CVE-2026-48796 is a MODERATE (CVSS 5.3) `folderschemehandlerfactory` path boundary check can vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting CefSharp.Common libraries in the NuGet ecosystem. The issue involves `folderschemehandlerfactory` path boundary check can expose files outside the configured root folder. Remediation is available by upgrading affected packages to version 148.0.90.

8 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:nuget/CefSharp.Common

8 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:nuget/CefSharp.Common. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-85jm-cwp2-mvpv CVE-2026-48796 MODERATE CefSharp.Common: `FolderSchemeHandlerFactory` path boundary check can expose files outside the configured root folder
GHSA-pv36-h7jh-qm62 CVE-2020-15999 MODERATE Heap buffer overflow in CefSharp
GHSA-4c29-gfrp-g6x9 - HIGH CefSharp affected by libvpx's heap buffer overflow in vp8 encoding
GHSA-j646-gj5p-p45g - CRITICAL CefSharp affected by heap buffer overflow in WebP
GHSA-m7mf-48hp-5qmr CVE-2020-16009 HIGH Inappropriate implementation in V8
GHSA-vv6j-ww6x-54gx CVE-2022-0609 HIGH Use after free in Animation
GHSA-x7fx-mcc9-27j7 CVE-2020-16013 HIGH Inappropriate implementation in V8 in CefSharp
GHSA-gvqv-779r-4jgp CVE-2020-16017 HIGH Use after free in CefSharp

CVE-2026-48796 at a Glance

CVE Identifier CVE-2026-48796
GHSA Identifier GHSA-85jm-cwp2-mvpv
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product CefSharp.Common
Package Ecosystem NuGet
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-48796

To remediate this vulnerability, upgrade all affected CefSharp.Common dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

CefSharp.Common fixed: 148.0.90
Upgrade CefSharp.Common to 148.0.90
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for CefSharp.Common

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-48796, inspect your project dependencies for CefSharp.Common:

inspect dependencies for CefSharp.Common

Analyze the terminal output to locate any version of CefSharp.Common in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 148.0.90), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In CefSharp.Common, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary `FolderSchemeHandlerFactory` was intended to restrict served files to a configured `rootFolder`, but its path validation used a raw string prefix check. A request could escape to a sibling directory whose full path starts with the root folder path, allowing files outside the configured root to be served. ### Details In affected versions, `FolderSchemeHandlerFactory` canonicalized `rootFolder`, decoded the request path, combined it with the root, and then allowed the file when: ```csharp filePath.StartsWith(rootFolder, StringComparison.OrdinalIgnoreCase) ``` This does not enforce a directory boundary. For example, `/tmp/app/www2/secret.txt` starts with `/tmp/app/www`, but `www2` is a sibling of `www`, not a child. The same issue applies on Windows, for example `C:\app\www2\secret.txt` starts with `C:\app\www`. The affected code was reviewed at commit `b5fef3bb4bc58798c95170078c41de92cfe9066e`, assembly version `147.0.100`. ### PoC Set `rootFolder` to a directory named `www` and create a sibling directory named `www2`: ```text <temp>/www/index.html <temp>/www2/secret.txt ``` Register `FolderSchemeHandlerFactory` for `<temp>/www`, then request: ```text https://folderschemehandlerfactory.test/..%2fwww2/secret.txt ``` The request path is URL-decoded to `../www2/secret.txt`, combined with `<temp>/www`, and canonicalized to: ```text <temp>/www2/secret.txt ``` Because `<temp>/www2/secret.txt` starts with `<temp>/www` as a string prefix, the affected check passes and `secret.txt` is served from outside `rootFolder`. Expected vulnerable result: HTTP 200 with the contents of `<temp>/www2/secret.txt`. Expected fixed result: 404 or equivalent not-found response because the resolved file is outside `rootFolder`. ### Impact Applications using `FolderSchemeHandlerFactory` for a custom scheme or registered HTTP/HTTPS scheme may expose local files outside the intended served directory. This is most relevant when sensitive sibling directories share the root path prefix, such as `www`/`www2`, `public`/`public_backup`, or `static`/`static-secrets`. An attacker must be able to cause the embedded browser to request URLs handled by the affected scheme registration.

CVE-2026-48796 Affected CefSharp.Common Versions

1 component(s)
Fixed Versions:
148.0.90
Product / Package Ecosystem Affected Versions Fixed Version
CefSharp.Common
NuGet
< 148.0.90
148.0.90

References

Frequently Asked Questions

What is CVE-2026-48796?
CVE-2026-48796 is a security vulnerability in CefSharp.Common involving `FolderSchemeHandlerFactory` path boundary check can expose files outside the configured root folder under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which CefSharp.Common versions are affected?
Affected versions include releases prior to 148.0.90 across affected packages: CefSharp.Common.
What version fixes CVE-2026-48796?
Upgrading to 148.0.90 (or the latest patched release for your respective branch) resolves the vulnerability.
Is CefSharp.Common affected?
Yes, CefSharp.Common is affected in releases prior to 148.0.90. Upgrade your dependency to 148.0.90 or later.
What is the CVSS score of CVE-2026-48796?
CVE-2026-48796 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-48796?
CVE-2026-48796 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check NuGet dependencies for CVE-2026-48796?
Run the dependency tree command: 'inspect dependencies for CefSharp.Common'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-85jm-cwp2-mvpv",
  "modified" : "2026-06-30T18:36:12Z",
  "published" : "2026-06-30T18:36:12Z",
  "aliases" : [ "CVE-2026-48796" ],
  "summary" : "CefSharp.Common: `FolderSchemeHandlerFactory` path boundary check can expose files outside the configured root folder",
  "details" : "### Summary\n\n`FolderSchemeHandlerFactory` was intended to restrict served files to a configured `rootFolder`, but its path validation used a raw string prefix check. A request could escape to a sibling directory whose full path starts with the root folder path, allowing files outside the configured root to be served.\n\n### Details\n\nIn affected versions, `FolderSchemeHandlerFactory` canonicalized `rootFolder`, decoded the request path, combined it with the root, and then allowed the file when:\n\n```csharp\nfilePath.StartsWith(rootFolder, StringComparison.OrdinalIgnoreCase)\n```\n\nThis does not enforce a directory boundary. For example, `/tmp/app/www2/secret.txt` starts with `/tmp/app/www`, but `www2` is a sibling of `www`, not a child. The same issue applies on Windows, for example `C:\\app\\www2\\secret.txt` starts with `C:\\app\\www`.\n\nThe affected code was reviewed at commit `b5fef3bb4bc58798c95170078c41de92cfe9066e`, assembly version `147.0.100`.\n\n### PoC\n\nSet `rootFolder` to a directory named `www` and create a sibling directory named `www2`:\n\n```text\n<temp>/www/index.html\n<temp>/www2/secret.txt\n```\n\nRegister `FolderSchemeHandlerFactory` for `<temp>/www`, then request:\n\n```text\nhttps://folderschemehandlerfactory.test/..%2fwww2/secret.txt\n```\n\nThe request path is URL-decoded to `../www2/secret.txt`, combined with `<temp>/www`, and canonicalized to:\n\n```text\n<temp>/www2/secret.txt\n```\n\nBecause `<temp>/www2/secret.txt` starts with `<temp>/www` as a string prefix, the affected check passes and `secret.txt` is served from outside `rootFolder`.\n\nExpected vulnerable result: HTTP 200 with the contents of `<temp>/www2/secret.txt`.\n\nExpected fixed result: 404 or equivalent not-found response because the resolved file is outside `rootFolder`.\n\n### Impact\n\nApplications using `FolderSchemeHandlerFactory` for a custom scheme or registered HTTP/HTTPS scheme may expose local files outside the intended served directory. This is most relevant when sensitive sibling directories share the root path prefix, such as `www`/`www2`, `public`/`public_backup`, or `static`/`static-secrets`.\n\nAn attacker must be able to cause the embedded browser to request URLs handled by the affected scheme registration.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "NuGet",
      "name" : "CefSharp.Common"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "148.0.90"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/cefsharp/CefSharp/security/advisories/GHSA-85jm-cwp2-mvpv"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/cefsharp/CefSharp"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-30T18:36:12Z",
    "nvd_published_at" : null
  }
}