How severe is CVE-2020-15999?

CVE-2020-15999 has a CVSS score of 9.6/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-15999?

CVE-2020-15999 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-15999?

Update CefSharp.Common to version 85.3.130 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is CVE-2020-15999 actively exploited in the wild?

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

CVE-2020-15999 has an EPSS (Exploit Prediction Scoring System) score of 93.0%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

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

Yes. CVE-2020-15999 (Google Chrome FreeType Heap Buffer Overflow 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 2021-11-17. 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-15999?

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

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

CVE-2020-15999 was published on November 3, 2020 and was last updated on April 16, 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 2021-11-17

.NET NuGet

CVE-2020-15999

CRITICAL

Heap buffer overflow in CefSharp

Also known asA-171232105ASB-A-171232105GHSA-pv36-h7jh-qm62

Published

Nov 3, 2020

Updated

Apr 16, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

7 known

EPSS Exploitation Probability

via FIRST.org ↗

93.0%probability of exploitation in next 30 days

Very High Risk100th 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

Heap buffer overflow in Freetype in Google Chrome prior to 86.0.4240.111 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	85.3.130
.NETNuGet	`CefSharp.Wpf`	all versions	85.3.130
.NETNuGet	`CefSharp.WinForms`	all versions	85.3.130
.NETNuGet	`CefSharp.Wpf.HwndHost`	all versions	85.3.130

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.