Skip to content
skopnix

CVE-2020-6418 · Published 27 Feb 2020

Google Chromium V8

On CISA's KEV list 615 days after disclosure; 6 public exploits.

Google Chromium V8 Engine contains a type confusion vulnerability allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.

CISA required action (federal due date 3 May 2022): Apply updates per vendor instructions.

Signals

KEV, exploited in the wild
yes, added 3 Nov 2021, due 3 May 2022
EPSS, 30-day forecast
79%, 100th percentile (as of 18 Nov 2026)
CVSS, NVD
not stated
Internet exposure
not stated

KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.

Timeline 27 Feb 2020 to today

604 days from the first proof of concept to the KEV listing
20212023202420252026Disclosed 27 Feb 2020Metasploit 29 Feb 2020First PoC 9 Mar 2020KEV 3 Nov 2021today
  1. Disclosed
  2. Metasploit+2 d
  3. First PoC+9 d
  4. KEV+604 d

604 days from the first proof of concept to the KEV listing

Indicators none tied yet

No threat feed has tied an indicator to this CVE yet. Checked every six hours.

On the wire 0 dispatches

No dispatch on our wire has named this CVE yet.

Public exploit code 6 known · links only

GitHub PoCs 4Metasploit 1Exploit-DB 1

GitHub PoCs, by trust then stars4

  1. first seen by skopnix 18 Oct 2026

  2. first seen by skopnix 18 Oct 2026

  3. first seen by skopnix 18 Oct 2026

  4. first seen by skopnix 18 Oct 2026

Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.

Metasploit1

  1. This module exploits an issue in Google Chrome 80.0.3987.87 (64 bit). The exploit corrupts the length of a float array (float_rel), which can then be used for out of bounds read and write on adjacent memory. The relative read and write is then used to modify a UInt64Array (uint64_aarw) which is used for read and writing from absolute memory. The exploit then uses WebAssembly in order to allocate a region of RWX memory, which is then rep

    ruby · first seen by skopnix 18 Oct 2026

Exploit-DB1

  1. created 9 Mar 2020

References

Watch this one?

KEV additions reach Telegram and the KEV-only RSS as they land.

Telegram ↗KEV RSSAPIStack check