# CVE-2020-6418: Google Chromium V8 Type Confusion

> A remote attacker can exploit heap corruption via a crafted HTML page due to type confusion in V8, potentially executing arbitrary code.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Feb 2020
- **Updated:** 21 Oct 2025
- **Also known as:** DEBIAN-CVE-2020-6418, GHSA-495j-4jmx-mgrx, UBUNTU-CVE-2020-6418

## What is CVE-2020-6418?

CVE-2020-6418 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 27 Feb 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2020-6418?

It affects 6 products.


Products: Debian Debian Linux, Fedoraproject Fedora, Google Chrome, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation.

## How do I fix CVE-2020-6418?

Upgrade to a fixed version. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-6418 being exploited?

Yes. Attackers have exploited CVE-2020-6418 in the wild since at least 3 Nov 2021.

Public exploit code:

- for 供養 (github_poc): https://github.com/Goyotan/CVE-2020-6418-PoC
- An exploit for CVE-2020-6418 implementing a SHELF Loader. Published as part of Tmp.0ut volume 2 (github_poc): https://github.com/ulexec/ChromeSHELFLoader
- https://github.com/SivaPriyaRanganatha/CVE-2020-6418 (github_poc): https://github.com/SivaPriyaRanganatha/CVE-2020-6418
- Google Chrome 80 JSCreate side-effect type confusion exploit (metasploit)
- PoC of CVE (github_poc): https://github.com/ASkyeye/CVE-2020-6418
- Google Chrome 80 - JSCreate Side-effect Type Confusion (Metasploit) (exploitdb)

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6418 and fix it if it is affected.

What it is: CVE-2020-6418 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 27 Feb 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2020-6418 in the wild since at least 3 Nov 2021.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-6418/ (Markdown: https://insights.sbomify.com/CVE-2020-6418/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-6418
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-6418
- OSV: https://osv.dev/vulnerability/CVE-2020-6418

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-6418/
Summaries are generated and may contain mistakes; the official description above is the record.