CefSharp affected by heap buffer overflow in WebP

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Google is aware that an exploit for CVE-2023-4863 exists in the wild. Description Heap buffer overflow in WebP in Google Chrome prior to 116.0.5845.187 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Critical) References - https://www.cve.org/CVERecord?id=CVE-2023-4863 - https://nvd.nist.gov/vuln/detail/CVE-2023-4863 - https://www.techtarget.com/searchsecurity/news/366551978/Browser-companies-patch-critical-zero-day-vulnerability --- Updated There is another related security vulnerability. There's another related CVE (CVE-2023-5217) that is fixed in Chromium 117.0.5938.132. This one is triggered by WebCodecs API encoder usage, so a workaround for older versions is to disable the WebCodecs API (--disable-blink-features=WebCodecs). As per https://magpcss.org/ceforum/viewtopic.php?f=6&t=19551#p54150

Published by the source

21 Sep 2023, 17:11 UTC

Last modified by the source

2 Oct 2023, 20:17 UTC

Source last checked

26 Oct 2026, 16:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j646-gj5p-p45g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-j646-gj5p-p45g

Advisory: CefSharp affected by heap buffer overflow in WebP
IDs: GHSA-j646-gj5p-p45g
Record: https://patchnext.com/advisories/ghsa-j646-gj5p-p45g (revision 1, source checked 26 Oct 2026, 16:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: cefsharp.common.netcore 116.0.230; cefsharp.common 116.0.230. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet cefsharp.common.netcore: affected < 116.0.230; fixed in 116.0.230
- NuGet cefsharp.common: affected < 116.0.230; fixed in 116.0.230

## Suggested inspection (read-only)
- NuGet cefsharp.common.netcore: check the installed version with your package manager.
- NuGet cefsharp.common: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on cefsharp.common.netcore, cefsharp.common.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j646-gj5p-p45g (GitHub-reviewed advisory GHSA-j646-gj5p-p45g lists affected ranges: NuGet cefsharp.common >=0 =0 <116.0.230)

Commands are suggestions: review each one before running it.