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

Q: How do I fix CVE-2020-16013?

chrome: upgrade to 86.0.4240.198. Exact commands for each OS are on this page.

Q: Is CVE-2020-16013 being exploited?

Yes. CVE-2020-16013 is on the CISA Known Exploited Vulnerabilities list, so treat it as patch-now.

Q: What does CVE-2020-16013 affect?

CVE-2020-16013 affects chrome. Severity is high (CVSS 8.8). 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.

Q: How urgent is CVE-2020-16013?

Priority 77/100. High severity; Exploited in the wild (CISA KEV)

Patch now

HIGH 8.8EXPLOITEDUPGRADE

CVE-2020-16013 is a high-severity flaw (CVSS 8.8) affecting chrome, reported as exploited in the wild. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Exploited in the wild (CISA KEV)

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	2.8% (top 14%)
CISA exploited list	Yes, fix due 2022-05-03
Weakness	CWE-787
Published	2021-01-08
Last modified	2026-06-17

Publisher (CNA): Chrome · Vendor: google

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-01-08 19:15 UTCPublished CVE record published
2021-11-03Exploited Added to the CISA Known Exploited Vulnerabilities list
2022-05-03Deadline CISA due date for US federal agencies to patch
2026-06-17 02:57 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 86.0.4240.198

Fixed in: 86.0.4240.198

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy chrome || rpm -q chrome || chrome --version

2. UPGRADE to 86.0.4240.198 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade chrome

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade chrome

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Exact fixes by distribution

NuGet (.NET) · CefSharp.Common · FIXED · 86.0.241 · vulnerable: < 86.0.241 · source

dotnet add package CefSharp.Common --version 86.0.241

NuGet (.NET) · CefSharp.Wpf · FIXED · 86.0.241 · vulnerable: < 86.0.241 · source

dotnet add package CefSharp.Wpf --version 86.0.241

NuGet (.NET) · CefSharp.WinForms · FIXED · 86.0.241 · vulnerable: < 86.0.241 · source

dotnet add package CefSharp.WinForms --version 86.0.241

NuGet (.NET) · CefSharp.Wpf.HwndHost · FIXED · 86.0.241 · vulnerable: < 86.0.241 · source

dotnet add package CefSharp.Wpf.HwndHost --version 86.0.241

Fedora 46 · python-dtoc · FIXED · 0.1.0-1.fc46 · FEDORA-2026-e4734649a1 · source

sudo dnf upgrade --advisory=FEDORA-2026-e4734649a1

Fedora ELN · parallel · FIXED · 20261022-1.eln159 · FEDORA-2026-6d961c0286 · source

sudo dnf upgrade --advisory=FEDORA-2026-6d961c0286

Debian 12 · chromium · FIXED · 87.0.4280.88-0.1

sudo apt update && sudo apt install --only-upgrade chromium dpkg --compare-versions "$(dpkg-query -W -f='${Version}' chromium)" ge "87.0.4280.88-0.1" && echo PATCHED || echo STILL-VULNERABLE

Debian 13 · chromium · FIXED · 87.0.4280.88-0.1

sudo apt update && sudo apt install --only-upgrade chromium dpkg --compare-versions "$(dpkg-query -W -f='${Version}' chromium)" ge "87.0.4280.88-0.1" && echo PATCHED || echo STILL-VULNERABLE

RHEL 6 Supplementary · chromium-browser · FIXED · chromium-browser-86.0.4240.198-1.el6_10

sudo dnf upgrade --advisory=RHSA-2020:5165 rpm -q chromium-browser

Verify at the official source NVD · CVE Program · CISA KEV catalog · Report a problem with this page
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-16013?

chrome: upgrade to 86.0.4240.198. Exact commands for each OS are on this page.

Is CVE-2020-16013 being exploited?

Yes. CVE-2020-16013 is on the CISA Known Exploited Vulnerabilities list, so treat it as patch-now.

What does CVE-2020-16013 affect?

CVE-2020-16013 affects chrome. Severity is high (CVSS 8.8). 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.

How urgent is CVE-2020-16013?

Priority 77/100. High severity; Exploited in the wild (CISA KEV)

Software pages

Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-76031 HIGH 8.8 UPGRADE Use after free in Input in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to execute arbitrary
CVE-2026-76030 HIGH 8.8 UPGRADE Memory corruption in FileSystem in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to potential
CVE-2026-76029 HIGH 8.8 UPGRADE Memory corruption in Network in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to potentially
CVE-2026-76028 HIGH 8.8 UPGRADE Use after free in FileSystem in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to execute arbi
CVE-2026-76026 HIGH 8.8 UPGRADE Memory corruption in Autofill in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to execute arb

References

← Back to latest CVEs