How severe is GHSA-gvqv-779r-4jgp?

No CVSS score has been assigned to GHSA-gvqv-779r-4jgp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gvqv-779r-4jgp?

GHSA-gvqv-779r-4jgp affects the following packages: CefSharp.Common (NuGet), CefSharp.Wpf (NuGet), CefSharp.WinForms (NuGet), CefSharp.Wpf.HwndHost (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-gvqv-779r-4jgp?

Update CefSharp.Common to 86.0.241 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gvqv-779r-4jgp is resolved across your whole dependency graph.

How do I detect GHSA-gvqv-779r-4jgp in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for CefSharp.Common. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-gvqv-779r-4jgp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-gvqv-779r-4jgp?

O3 pinpoints whether GHSA-gvqv-779r-4jgp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-gvqv-779r-4jgp actively exploited in the wild?

Yes. There are 3 known exploit references for GHSA-gvqv-779r-4jgp, including 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-gvqv-779r-4jgp?

GHSA-gvqv-779r-4jgp has an EPSS (Exploit Prediction Scoring System) score of 2.7%, placing it in the 85th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is GHSA-gvqv-779r-4jgp in the CISA Known Exploited Vulnerabilities catalog?

Yes. GHSA-gvqv-779r-4jgp (Google Chrome Use-After-Free Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is GHSA-gvqv-779r-4jgp?

GHSA-gvqv-779r-4jgp is classified as Use After Free (CWE-416). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-gvqv-779r-4jgp published, and has it been updated?

GHSA-gvqv-779r-4jgp was published on November 27, 2020 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2021-11-03 — agencies required to remediate by 2022-05-03

.NET NuGet

GHSA-gvqv-779r-4jgp

Use after free in CefSharp

Also known asCVE-2020-16017

Published

Nov 27, 2020

Updated

Dec 2, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

2.7%probability of exploitation in next 30 days

Lower Risk85th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected

.NETCefSharp.Common.NETCefSharp.Wpf.NETCefSharp.WinForms.NETCefSharp.Wpf.HwndHost

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

CVE-2020-16017: Use after free in site isolation

Google is aware of reports that exploits for CVE-2020-16013 and CVE-2020-16017 exist in the wild.

There is currently little to no public information on the issue other than it has been flagged as High severity.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`CefSharp.Common`	all versions	86.0.241
.NETNuGet	`CefSharp.Wpf`	all versions	86.0.241
.NETNuGet	`CefSharp.WinForms`	all versions	86.0.241
.NETNuGet	`CefSharp.Wpf.HwndHost`	all versions	86.0.241

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Use after free in site isolation in Google Chrome prior to 86.0.4240.198…

chromereleases.googleblog.comChromeNov 2020

Use after free in site isolation in Google Chrome prior to 86.0.4240.198…

chromereleases.googleblog.comGoogle-sheetNov 2020

Use after free in site isolation in Google Chrome prior to 86.0.4240.198…

cisa.govCISAJul 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for CefSharp.Common. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update CefSharp.Common to 86.0.241 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gvqv-779r-4jgp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-gvqv-779r-4jgp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-gvqv-779r-4jgp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

CVE-2020-16017: Use after free in site isolation - https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop_11.html - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16017 Google is aware of reports that exploits for CVE-2020-16013 and CVE-2020-16017 exist in the wild. There is currently little to no public information on the issue other than it has been flagged as `High` severity.

O3 Security · Impact-Aware SCA

Is GHSA-gvqv-779r-4jgp in your dependencies?

O3 detects GHSA-gvqv-779r-4jgp across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-gvqv-779r-4jgp

EPSS Exploitation Probability

Blast Radius

Description

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-gvqv-779r-4jgp in your dependencies?