CVE-2020-16013

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 — 3 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: 2.8%CVSS: 8.8Exploit: cisa kev · ssvc activeExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

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%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
2.8%
EPSS %ILE
85th
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

January 8, 2021

Last Modified

October 24, 2025

Advisory Details (3)

Auto-updated Jun 2, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa.
cisa🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-16013
generic
https://crbug.com/1147206
generic🔴 Active Exploitation

Chrome Releases: Stable Channel Update for Desktop

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatchromium-browser-0:86.0.4240.198-1.el6_102020-11-23redhat

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 rangeFix by version rangeDependents
CefSharp.Common31.0.0-pre1 ... 86.0.240-pre (87 versions)
  • every version up to 86.0.241: fixed in 86.0.241
—
CefSharp.WinForms1.25.3 ... 86.0.240-pre (86 versions)
  • every version up to 86.0.241: fixed in 86.0.241
—
CefSharp.Wpf1.25.2-perlun0 ... 86.0.240-pre (94 versions)
  • every version up to 86.0.241: fixed in 86.0.241
—
CefSharp.Wpf.HwndHost83.4.20-pre, 84.4.10, 85.3.121, 85.3.130
  • every version up to 86.0.241: fixed in 86.0.241
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
chromium73.0.3683.75-1 ... 87.0.4280.88-0.3 (47 versions)
  • every version up to 87.0.4280.88-0.4~deb10u1: fixed in 87.0.4280.88-0.4~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 87.0.4280.88-0.1: fixed in 87.0.4280.88-0.1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 87.0.4280.88-0.1: fixed in 87.0.4280.88-0.1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 87.0.4280.88-0.1: fixed in 87.0.4280.88-0.1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 87.0.4280.88-0.1: fixed in 87.0.4280.88-0.1
—

Weakness Classification(1)

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 60× in last 7d / 266× 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 1,146 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(6)

What is CVE-2020-16013?
CVE-2020-16013 is a critical vulnerability published on January 8, 2021. Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.198 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
When was CVE-2020-16013 disclosed?
CVE-2020-16013 was first published on January 8, 2021, 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-16013 actively exploited?
Yes. CISA added CVE-2020-16013 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 attention. A fix is available. Apply it.
What is the CVSS score of CVE-2020-16013?
CVE-2020-16013 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 (CRITICAL).
Which products are affected by CVE-2020-16013?
CVE-2020-16013 affects Google Chromium V8. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2020-16013?
A fix for CVE-2020-16013 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2020-16013?

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

Book a Demo →Browse All CVEs