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

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.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
3%
EPSS %ILE
85%
KEV
⚠ Exploited

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 Patch Available🔴 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 / EcosystemFixed in / 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

(4 across 1 ecosystem)
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—

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 46× in last 7d / 243× 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 484 total refreshes for this CVE.

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

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 in the National Vulnerability Database 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 patching attention.
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.
Which products are affected by CVE-2020-16013?
CVE-2020-16013 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-16013?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-16013, 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-16013

Explore →

Is Your Infrastructure Affected by CVE-2020-16013?

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

Start Free Scan →Browse All CVEs