How severe is CVE-2020-16009?

CVE-2020-16009 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-16009?

CVE-2020-16009 affects the following packages: CefSharp.Common (NuGet), CefSharp.Wpf (NuGet), CefSharp.WinForms (NuGet), CefSharp.Wpf.HwndHost (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2020-16009?

Update CefSharp.Common to 86.0.241 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-16009 is resolved across your whole dependency graph.

How do I detect CVE-2020-16009 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 CVE-2020-16009 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 CVE-2020-16009?

O3 pinpoints whether CVE-2020-16009 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 CVE-2020-16009 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2020-16009, including 5 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 CVE-2020-16009?

CVE-2020-16009 has an EPSS (Exploit Prediction Scoring System) score of 48.6%, placing it in the 99th 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 warrants monitoring and prompt remediation.

Is CVE-2020-16009 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2020-16009 (Google Chromium V8 Type Confusion 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 CVE-2020-16009?

CVE-2020-16009 is classified as Out-of-bounds Write (CWE-787), CWE-843 (CWE-843). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-16009 published, and has it been updated?

CVE-2020-16009 was published on November 3, 2020 and was last updated on July 8, 2026. 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

CVE-2020-16009

HIGH

Inappropriate implementation in V8

Also known asGHSA-m7mf-48hp-5qmr

Published

Nov 3, 2020

Updated

Jul 8, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

5 known

EPSS Exploitation Probability

via FIRST.org ↗

48.6%probability of exploitation in next 30 days

High Risk99th 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

Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.183 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

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.