CVE-2020-6418

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, ghsa, nvd
Trending — 5 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: 79%CVSS: 8.8Exploit: cisa kev · ssvc active · Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

Type confusion in V8 in Google Chrome prior to 80.0.3987.122 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
79%
EPSS %ILE
100%
KEV
⚠ Exploited

Published

February 27, 2020

Last Modified

October 24, 2025

Advisory Details (8)

Auto-updated Jun 2, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: redhat.
redhat Patch Available

Affected: Red Hat Enterprise Linux 6 Supplementary.

https://access.redhat.com/errata/RHSA-2020:0738
generic

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

https://www.debian.org/security/2020/dsa-4638
generic

Chromium, Google Chrome: Multiple vulnerabilities (GLSA 202003-08) — Gentoo security

https://security.gentoo.org/glsa/202003-08
generic

[SECURITY] Fedora 31 Update: chromium-80.0.3987.132-1.fc31 - package-announce - Fedora mailing-lists

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

[SECURITY] Fedora 30 Update: chromium-80.0.3987.149-1.fc30 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6IOHSO6BUKC6I66J5PZOMAGFVJ66ZS57/
generic🔴 Active Exploitation

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop_24.html

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatchromium-browser-0:80.0.3987.122-1.el6_102020-03-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.

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 62× in last 7d / 359× 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 732 total refreshes for this CVE.

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

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCulexec/ChromeSHELFLoader
    First seen Feb 19, 2022

    An exploit for CVE-2020-6418 implementing a SHELF Loader. Published as part of Tmp.0ut volume 2

    Open source ↗
  • GitHub PoCGoyotan/CVE-2020-6418-PoC
    First seen Jun 13, 2020

    for 供養

    Open source ↗
  • Exploit-DBEDB-48186✓ verified
    First seen Mar 9, 2020

    Google Chrome 80 - JSCreate Side-effect Type Confusion (Metasploit)

    Open source ↗
  • Metasploitexploit/multi/browser/chrome_jscreate_sideeffect✓ verified
    First seen Feb 19, 2020

    Google Chrome 80 JSCreate side-effect type confusion exploit

    Open source ↗

Frequently asked(6)

What is CVE-2020-6418?
CVE-2020-6418 is a critical vulnerability published on February 27, 2020. Type confusion in V8 in Google Chrome prior to 80.0.3987.122 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
When was CVE-2020-6418 disclosed?
CVE-2020-6418 was first published in the National Vulnerability Database on February 27, 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-6418 actively exploited?
Yes. CISA added CVE-2020-6418 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-6418?
CVE-2020-6418 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-6418?
CVE-2020-6418 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-6418?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-6418, 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

Explore the affected products and dependency analysis for CVE-2020-6418

Explore →

Is Your Infrastructure Affected by CVE-2020-6418?

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