CVE-2020-16009

CRITICALNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 48%CVSS: 8.8Exploit: cisa kev · ssvc active · epss top5pctExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
9.0(high)
EG Risk
81(Attend)
EG Risk 81/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
48%
EPSS %ILE
99%
KEV
⚠ Exploited

Published

November 3, 2020

Last Modified

October 24, 2025

Advisory Details (7)

Auto-updated Jun 2, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic

[SECURITY] [DSA 4824-1] chromium security update

https://www.debian.org/security/2021/dsa-4824
generic

Chromium, Google Chrome: Multiple vulnerabilities (GLSA 202011-12) — Gentoo security

https://security.gentoo.org/glsa/202011-12
generic

[SECURITY] Fedora 33 Update: chromium-86.0.4240.183-1.fc33 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SC3U3H6AISVZB5PLZLLNF4HMQ4UFFL7M/
generic

[SECURITY] Fedora 32 Update: chromium-87.0.4280.66-1.fc32 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/S4XYJ7B6OXHZNYSA5J3DBUOFEC6WCAGW/
generic
https://crbug.com/1143772
generic🔴 Active Exploitation

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop.html
generic

Packet Storm

http://packetstormsecurity.com/files/159974/Chrome-V8-Turbofan-Type-Confusion.html

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatchromium-browser-0:86.0.4240.183-1.el6_102020-11-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 6 ecosystems)
NuGet(4)
PackageVulnerable rangeFixed inDependents
CefSharp.Common31.0.0-pre1 ... 86.0.240-pre (87 versions)86.0.241—
CefSharp.WinForms1.25.3 ... 86.0.240-pre (86 versions)86.0.241—
CefSharp.Wpf1.25.2-perlun0 ... 86.0.240-pre (94 versions)86.0.241—
CefSharp.Wpf.HwndHost83.4.20-pre, 84.4.10, 85.3.121, 85.3.13086.0.241—
Debian:10(1)
PackageVulnerable rangeFixed inDependents
chromium73.0.3683.75-1 ... 87.0.4280.88-0.3 (47 versions)87.0.4280.88-0.4~deb10u1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
chromium—87.0.4280.88-0.1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
chromium—87.0.4280.88-0.1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium—87.0.4280.88-0.1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium—87.0.4280.88-0.1—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 52× in last 7d / 226× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 818 total refreshes for this CVE.

  1. 2026-09-19 15:07 UTCVendor advisory
  2. 2026-09-19 10:45 UTCVendor advisory
  3. 2026-09-19 06:25 UTCVendor advisory
  4. 2026-09-19 02:05 UTCVendor advisory
  5. 2026-09-18 21:45 UTCEG score recompute
  6. 2026-09-18 21:45 UTCVendor advisory
  7. 2026-09-18 19:23 UTCEPSS rescore
  8. 2026-09-18 19:20 UTCCISA KEV update
  9. 2026-09-18 17:25 UTCVendor advisory
  10. 2026-09-18 14:15 UTCCISA KEV update
  11. 2026-09-18 13:04 UTCVendor advisory
  12. 2026-09-18 08:44 UTCVendor advisory
  13. 2026-09-18 04:24 UTCVendor advisory
  14. 2026-09-18 00:04 UTCVendor advisory
  15. 2026-09-17 19:44 UTCEG score recompute
  16. 2026-09-17 19:44 UTCVendor advisory
  17. 2026-09-17 19:22 UTCEPSS rescore
  18. 2026-09-17 19:22 UTCEPSS rescore
  19. 2026-09-17 15:24 UTCVendor advisory
  20. 2026-09-17 11:03 UTCVendor advisory
  21. 2026-09-17 06:42 UTCVendor advisory
  22. 2026-09-17 02:22 UTCVendor advisory
  23. 2026-09-16 22:00 UTCVendor advisory
  24. 2026-09-16 17:40 UTCEG score recompute
  25. 2026-09-16 17:40 UTCVendor advisory
Show 75 more
  1. 2026-09-16 14:10 UTCCISA KEV update
  2. 2026-09-16 14:04 UTCEPSS rescore
  3. 2026-09-16 13:17 UTCVendor advisory
  4. 2026-09-16 08:56 UTCEG score recompute
  5. 2026-09-16 08:56 UTCVendor advisory
  6. 2026-09-16 04:36 UTCVendor advisory
  7. 2026-09-16 00:16 UTCVendor advisory
  8. 2026-09-15 19:55 UTCVendor advisory
  9. 2026-09-15 15:35 UTCVendor advisory
  10. 2026-09-15 11:15 UTCVendor advisory
  11. 2026-09-15 06:55 UTCVendor advisory
  12. 2026-09-15 02:35 UTCVendor advisory
  13. 2026-09-14 22:14 UTCVendor advisory
  14. 2026-09-14 19:24 UTCCISA KEV update
  15. 2026-09-14 17:53 UTCVendor advisory
  16. 2026-09-14 13:33 UTCVendor advisory
  17. 2026-09-14 09:13 UTCVendor advisory
  18. 2026-09-14 04:53 UTCVendor advisory
  19. 2026-09-14 00:33 UTCVendor advisory
  20. 2026-09-13 20:13 UTCVendor advisory
  21. 2026-09-13 15:53 UTCVendor advisory
  22. 2026-09-13 11:33 UTCVendor advisory
  23. 2026-09-13 07:12 UTCVendor advisory
  24. 2026-09-13 02:53 UTCVendor advisory
  25. 2026-09-12 22:33 UTCVendor advisory
  26. 2026-09-12 18:13 UTCEG score recompute
  27. 2026-09-12 18:13 UTCVendor advisory
  28. 2026-09-12 14:56 UTCEPSS rescore
  29. 2026-09-12 13:53 UTCVendor advisory
  30. 2026-09-12 09:33 UTCVendor advisory
  31. 2026-09-12 05:13 UTCVendor advisory
  32. 2026-09-12 00:53 UTCVendor advisory
  33. 2026-09-11 20:33 UTCVendor advisory
  34. 2026-09-11 18:49 UTCCISA KEV update
  35. 2026-09-11 16:13 UTCVendor advisory
  36. 2026-09-11 11:53 UTCEG score recompute
  37. 2026-09-11 11:53 UTCVendor advisory
  38. 2026-09-11 09:32 UTCEPSS rescore
  39. 2026-09-11 07:33 UTCVendor advisory
  40. 2026-09-11 03:13 UTCVendor advisory
  41. 2026-09-10 22:53 UTCVendor advisory
  42. 2026-09-10 19:28 UTCCISA KEV update
  43. 2026-09-10 18:33 UTCVendor advisory
  44. 2026-09-10 14:13 UTCVendor advisory
  45. 2026-09-10 09:53 UTCEG score recompute
  46. 2026-09-10 09:53 UTCVendor advisory
  47. 2026-09-10 09:29 UTCEPSS rescore
  48. 2026-09-10 05:33 UTCVendor advisory
  49. 2026-09-10 01:13 UTCVendor advisory
  50. 2026-09-09 20:53 UTCVendor advisory
  51. 2026-09-09 19:08 UTCCISA KEV update
  52. 2026-09-09 16:32 UTCVendor advisory
  53. 2026-09-09 12:06 UTCVendor advisory
  54. 2026-09-09 07:46 UTCVendor advisory
  55. 2026-09-09 03:25 UTCVendor advisory
  56. 2026-09-08 23:05 UTCEG score recompute
  57. 2026-09-08 23:05 UTCVendor advisory
  58. 2026-09-08 21:56 UTCEPSS rescore
  59. 2026-09-08 18:54 UTCCISA KEV update
  60. 2026-09-08 18:45 UTCVendor advisory
  61. 2026-09-08 14:25 UTCVendor advisory
  62. 2026-09-08 10:04 UTCVendor advisory
  63. 2026-09-08 05:42 UTCVendor advisory
  64. 2026-09-08 01:22 UTCVendor advisory
  65. 2026-09-07 21:02 UTCVendor advisory
  66. 2026-09-07 16:42 UTCVendor advisory
  67. 2026-09-07 12:22 UTCVendor advisory
  68. 2026-09-07 08:01 UTCVendor advisory
  69. 2026-09-07 03:39 UTCVendor advisory
  70. 2026-09-06 23:14 UTCVendor advisory
  71. 2026-09-06 18:54 UTCVendor advisory
  72. 2026-09-06 14:34 UTCEG score recompute
  73. 2026-09-06 14:34 UTCVendor advisory
  74. 2026-09-06 13:44 UTCEPSS rescore
  75. 2026-09-06 10:14 UTCVendor advisory

Frequently asked(6)

What is CVE-2020-16009?
CVE-2020-16009 is a critical vulnerability published on November 3, 2020. 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.
When was CVE-2020-16009 disclosed?
CVE-2020-16009 was first published in the National Vulnerability Database on November 3, 2020, with the most recent update on October 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-16009 actively exploited?
Yes. CISA added CVE-2020-16009 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Google Chromium V8. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2020-16009?
CVE-2020-16009 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2020-16009?
CVE-2020-16009 affects Google Chromium V8. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2020-16009?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-16009, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-16009

Explore →

Is Your Infrastructure Affected by CVE-2020-16009?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs