CVE-2020-6418: Google Chromium V8 Type Confusion Vulnerability
CVE-2020-6418 is a high-severity flaw (CVSS 8.8) affecting chrome, fedora, enterprise linux desktop, reported as exploited in the wild. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- High severity
- EPSS top 1%: very likely to be exploited
- Exploited in the wild (CISA KEV)
- Public exploit reference
- On your watchlist
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.8 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 78.8% (top 1%) |
| CISA exploited list | Yes, fix due 2022-05-03 |
| Weakness | CWE-843 |
| Published | 2020-02-27 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Exploited Added to the CISA Known Exploited Vulnerabilities list
- Deadline CISA due date for US federal agencies to patch
- Updated Record last modified
Exact fixes by distribution
Public exploits and detection
Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.
- GitHub PoC: Goyotan/CVE-2020-6418-PoC (3 stars)
- GitHub PoC: ulexec/ChromeSHELFLoader (3 stars)
- GitHub PoC: SivaPriyaRanganatha/CVE-2020-6418 (1 stars)
- GitHub PoC: ASkyeye/CVE-2020-6418
- GitHub PoC: ChoKyuWon/CVE-2020-6418
- Exploit-DB: Google Chrome 80 - JSCreate Side-effect Type Confusion (Metasploit)
- Metasploit: Google Chrome 80 JSCreate side-effect type confusion exploit
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2020-6418?
chrome: upgrade to 80.0.3987.122; fedora: mitigate or apply the listed mitigation; enterprise linux desktop: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2020-6418 being exploited?
Yes. CVE-2020-6418 is on the CISA Known Exploited Vulnerabilities list, so treat it as patch-now.
What does CVE-2020-6418 affect?
CVE-2020-6418 affects chrome, fedora, enterprise linux desktop. Severity is high (CVSS 8.8). 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.
How urgent is CVE-2020-6418?
Priority 91/100. High severity; EPSS top 1%: very likely to be exploited; Exploited in the wild (CISA KEV); Public exploit reference; On your watchlist
Software pages
Debian vulnerabilities · Google Chrome vulnerabilities · Chromium vulnerabilities
Related CVEs
- CVE-2026-119260 HIGH 8.8 UPGRADE Use after free in Frames in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to execute arbitrar
- CVE-2026-119261 CRITICAL 9.6 UPGRADE Improper input validation in Skia in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to potenti
- CVE-2026-119262 HIGH 8.8 UPGRADE Improper input validation in V8 in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to potential
- CVE-2026-119263 CRITICAL 9.6 UPGRADE Memory corruption in GarbageCollection in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to po
- CVE-2026-119264 HIGH 8.8 UPGRADE Memory corruption in Dawn in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to potentially exe