EPSS Exploitation Probability
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
CefSharp.Common.NETCefSharp.Wpf.NETCefSharp.WinForms.NETCefSharp.Wpf.HwndHostReal-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-16009: Inappropriate implementation in V8
- https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop.html
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16009
Google is aware of reports that exploits for CVE-2020-16009 exist in the wild.
Allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
There is currently little to no public information on the issue other than it has been flagged as High severity.
Affected Packages
| 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 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.1…
Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.1…
Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.1…
Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.1…
Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.1…
Frequently Asked Questions
Is GHSA-m7mf-48hp-5qmr in your stack?
O3 detects GHSA-m7mf-48hp-5qmr across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.