Advisory record · GHSA-f87w-3j5w-v58p

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

CVSS 8.3 High

Published by the GitHub Advisory Database at 12 Apr 2025, 03:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
CefSharp.WpfNuGet<134.3.90134.3.90
CefSharp.Wpf.HwndHostNuGet<134.3.90134.3.90
CefSharp.Wpf.NetCoreNuGet<134.3.90134.3.90
CefSharp.WinFormsNuGet<134.3.90134.3.90
CefSharp.WinForms.NetCoreNuGet<134.3.90134.3.90
CefSharp.OffScreen.NetCoreNuGet<134.3.90134.3.90
CefSharp.OffScreenNuGet<134.3.90134.3.90
Identifiers
GHSA-f87w-3j5w-v58p
Published
12 Apr 2025
Updated
12 Apr 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

CefSharp packages (CefSharp.Wpf, CefSharp.WinForms, CefSharp.OffScreen and their .NET Core and HwndHost variants) before 134.3.90 on Windows are affected. The source describes an incorrect handle in Mojo, inherited from Google Chrome before 134.0.6998.177, that lets a remote attacker escape the sandbox through a malicious file. Upgrade the affected CefSharp packages to 134.3.90 or later.

Written 9 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.3 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 15:22 UTC First seen by agentprime
  2. 31 Oct 2026, 15:22 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.