CSIRTS // UNIFIED SECURITY ADVISORY FEEDSYS ● ONLINE · POWERED BY INTELFUSIONS.COM

CVE-2020-6418

criticalknown exploitedpublic exploitcovered by 1 sourcefirst seen 2021-11-03
Actively exploited. CVE-2020-6418 is listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03) — exploitation has been observed in the wild, and US federal agencies are required to remediate it under BOD 22-01. Treat patching as urgent.
Public exploit code is available. Proof-of-concept or working exploit code for CVE-2020-6418 is indexed in Metasploit, Exploit-DB and GitHub PoC. Expect opportunistic scanning and exploitation attempts — prioritize remediation.
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.

CSIRTS triage

What
Google Chromium V8 Engine contains a type confusion vulnerability that allows a remote attacker to potentially exploit heap corruption.
Who is affected
Users of web browsers utilizing the Chromium V8 Engine, including Google Chrome and Microsoft Edge.
Urgency
Remediation is urgent due to active exploitation and critical severity.
Action
Update to the latest version of affected web browsers.

AI-assisted analysis generated from the source advisory — verify against the original.

⚡ Watch CVE-2020-6418

Get an email if CVE-2020-6418 is added to CISA KEV, gains public exploit code, or a new advisory cites it — max one per day, one-click unsubscribe.

Exploitation outlook

Exploit availability

Public exploit or proof-of-concept code for CVE-2020-6418 is indexed in these free datasets. Available exploit code raises real-world risk independent of the CVSS score.

Advisory coverage (1)

External references

NVD record for CVE-2020-6418

CVE.org record

CISA KEV catalog

Embed the live status

CVE-2020-6418 live status badge — this badge updates automatically when the KEV or exploit status changes. How to embed it →

[![CVE-2020-6418 status](https://www.csirts.com/badge/CVE-2020-6418)](https://www.csirts.com/cve/CVE-2020-6418)