CVE-2020-6418: Google Chromium V8 Type Confusion
Google Chromium V8 · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 79%
- higher than 99.5% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2022-05-03
- Ubuntu priority
- medium
CVE-2020-6418 explained
CVE-2020-6418 is a type confusion flaw in the V8 JavaScript engine used by Google Chrome and Chromium before 80.0.3987.122. A crafted HTML page can trigger heap corruption. CISA lists it as known to be exploited, so unpatched browsers should be treated as a real risk.
Impact
A remote attacker who gets a user to open a crafted HTML page could potentially exploit heap corruption in V8. No privileges are needed, but user interaction is required. Successful exploitation could have high impact on confidentiality, integrity and availability within the browser's context. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03. Ransomware use is listed as unknown.
Who is affected
The chromium-browser source package is affected on Ubuntu 16.04 LTS and Ubuntu 18.04 LTS. Both have fixed versions in the standard archive: 80.0.3987.149-0ubuntu0.16.04.1 for Ubuntu 16.04 LTS and 80.0.3987.149-0ubuntu0.18.04.1 for Ubuntu 18.04 LTS. Ubuntu 16.04 LTS is end of life. Ubuntu 18.04 LTS has ended standard support and receives further fixes only through Ubuntu Pro (ESM).
Written with AI from the data on this page and checked against it automatically.
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.
CISA required action: Apply updates per vendor instructions.
CISA notes
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- Google ChromeAffectedFixed in
- < 80.0.3987.122
- 80.0.3987.122
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome |
|
|
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Ubuntu 18.04 LTS·chromium-browser
Fixed: 80.0.3987.149-0ubuntu0.18.04.1
Ubuntu 16.04 LTS·chromium-browser
ESM ended
Fixed: 80.0.3987.149-0ubuntu0.16.04.1
What to do
- Update
chromium-browserto80.0.3987.149-0ubuntu0.16.04.1or80.0.3987.149-0ubuntu0.18.04.1, or later, depending on the release. - Close and restart all running Chromium instances so the patched code is loaded.
- Plan an upgrade of Ubuntu 16.04 LTS systems to a supported release, as it is end of life.
- For Ubuntu 18.04 LTS, enable Ubuntu Pro (ESM) to keep receiving future security fixes, or upgrade to a supported release.
- Check other Chrome or Chromium installations not managed by the Ubuntu package and update them per vendor instructions.
Written with AI from the data on this page and checked against it automatically.
Check and fix on a server
Run on each Ubuntu or Debian server. Replace chromium-browser with the source package from the table above.
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="chromium-browser"'2. Compare each installed version with the fixed version for your release from the table
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the fix
sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="chromium-browser"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-843 Access of Resource Using Incompatible Type ('Type Confusion')
Questions about CVE-2020-6418
- Is this vulnerability exploited in practice?
- Yes. CISA lists CVE-2020-6418 in its Known Exploited Vulnerabilities catalog, added on 2021-11-03, with the required action to apply updates per vendor instructions. Whether it was used in ransomware campaigns is listed as unknown.
- Does a user have to do anything for an attack to work?
- Yes. User interaction is required. The attack relies on the user opening a crafted HTML page, for example by visiting a malicious website. No privileges on the system are needed.
- Is installing the update enough?
- Installing the fixed
chromium-browserpackage is required, but browser sessions already running keep using the old code. Restart Chromium after updating so the fix takes effect.
Written with AI from the data on this page and checked against it automatically.
References
Other advisories
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.