Skip to content
Server Security Center
KEVhigh8.8

CVE-2020-16013: Google Chromium V8 Incorrect Implementation Vulnerabililty

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)
2.8%
higher than 86.5% of all CVEs
Added to CISA KEV
2021-11-03
US federal due date 2022-05-03
Ubuntu priority
medium

CVE-2020-16013 explained

CVE-2020-16013 is an inappropriate implementation flaw in the V8 JavaScript engine used by Google Chrome before 86.0.4240.198. A crafted HTML page could let a remote attacker potentially exploit heap corruption. CISA lists it as a known exploited vulnerability, so unpatched browsers face 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. A successful attack could have a high impact on confidentiality, integrity and availability within the browser's security scope. CISA has confirmed exploitation in the wild. Whether it has been used in ransomware is unknown.

Who is affected

The chromium-browser source package is affected on Ubuntu 16.04 LTS and Ubuntu 18.04 LTS. Both releases have fixed versions in the standard archive: 86.0.4240.198-0ubuntu0.16.04.1 for Ubuntu 16.04 LTS and 86.0.4240.198-0ubuntu0.18.04.1 for Ubuntu 18.04 LTS. Ubuntu 16.04 LTS is end of life. Standard support for Ubuntu 18.04 LTS has ended, and further fixes there come only with Ubuntu Pro (ESM).

Written with AI from the data on this page and checked against it automatically.

Official description

Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.198 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 Chrome
    Affected
    • < 86.0.4240.198
    Fixed in
    • 86.0.4240.198

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.

What to do

  1. Update chromium-browser to 86.0.4240.198-0ubuntu0.18.04.1 or later on Ubuntu 18.04 LTS.
  2. Update chromium-browser to 86.0.4240.198-0ubuntu0.16.04.1 or later on Ubuntu 16.04 LTS.
  3. Close and restart all running browser instances so the patched code is loaded.
  4. Plan an upgrade of Ubuntu 16.04 LTS systems to a supported release. Use Ubuntu Pro (ESM) or upgrade for Ubuntu 18.04 LTS.
  5. Treat this as urgent, because CISA lists it as actively exploited.

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" ;; esac

3. 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-787 Out-of-bounds Write

Questions about CVE-2020-16013

Is this vulnerability being exploited?
Yes. CISA added CVE-2020-16013 to its Known Exploited Vulnerabilities catalog on 2021-11-03. Its required action is to apply updates per vendor instructions.
Do I need to restart anything after updating?
Yes. Browser processes that are already running keep using the old code. Users should fully close and reopen the browser after the package update.
How can a system be attacked?
A user has to open a crafted HTML page in a vulnerable browser. The attacker needs no privileges on the system.

Written with AI from the data on this page and checked against it automatically.

References

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.