Skip to main content
ExploitedIn CISA KEVFix available

CVE-2020-16013

Exploitation confirmed. First attested on 2021-11-03 by CISA-ADP, CISA KEV, GCVE · kevintel.

  • Published2021-01-08
  • Fixed in86.0.4240.198
  • WeaknessCWE-787

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2021-01-0819:15CVE publishedNVD
  2. 2021-11-03Added to the CISA KEV catalogCISA KEV
  3. 2021-11-03Listed as exploited by GCVEGCVE
  4. 2021-11-03Exploitation first reportedCISA KEV
  5. 2025-02-0314:21SSVC exploitation set to activeCISA-ADP

Observed activity

isMalicious corpus · updated 2026-11-03 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-16013?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-16013?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Google chrome
BranchAffectedFixed in
86.0< 86.0.4240.19886.0.4240.198
CefSharp.Common
BranchAffectedFixed in
86.0< 86.0.24186.0.241
CefSharp.WinForms
BranchAffectedFixed in
86.0< 86.0.24186.0.241

2 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As Chrome, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Google Chrome
    Affected
    • < 86.0.4240.198fixed in 86.0.4240.198custom

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2021-01-08

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • chromiumSUSE:Package Hub 15 SP2all versions · fixed in 86.0.4240.198-bp152.2.29.1
  • chromiumSUSE:Package Hub 15 SP2all versions · fixed in 86.0.4240.198-bp152.2.35.1
  • chromiumSUSE:Package Hub 15 SP1all versions · fixed in 86.0.4240.198-bp152.2.29.1
  • chromiumSUSE:Package Hub 15 SP1all versions · fixed in 86.0.4240.198-bp151.3.128.1
  • chromiumSUSE:Package Hub 15 SP1all versions · fixed in 86.0.4240.198-bp151.3.134.1
  • chromiumopenSUSE:Tumbleweedall versions · fixed in 113.0.5672.92-1.1
  • chromiumopenSUSE:Tumbleweedall versions · fixed in 93.0.4577.82-1.1
  • chromiumopenSUSE:Leap 15.2all versions · fixed in 86.0.4240.198-bp152.2.29.1

10 more package ranges on OSV.dev

Vendor advisories

  • CVE-2020-16013 Red Hat Product Security14 products fixed

    chromium-browser: Inappropriate implementation in V8

  • ICSA-23-264-05 CISA1 known affected

    Rockwell Automation Connected Components Workbench

    Connected Components Workbench: < R21

  • RHSA-2020:5165 Red Hat Product Security14 products fixed

    Red Hat Security Advisory: chromium-browser security update

Full record on NVD

Fix

  1. Update Google chrome to 86.0.4240.198
  2. CISA’s required action: Apply updates per vendor instructions.due 2022-05-03
  3. Vendor fix CISA ICSA-23-264-05 · 1 productRockwell Automation recommends users to update Connected Components Workbench to R21 and later.
  4. Vendor fix Red Hat Product Security RHSA-2020:5165 · 14 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, Chromium must be restarted for the changes to take effect.
  5. Mitigation from the vendor CISA ICSA-23-264-05 · 1 productCustomers using the affected software are encouraged to apply the risk mitigations, if possible.
  6. Mitigation from the vendor CISA ICSA-23-264-05 · 1 productAdditionally, Rockwell Automation encourages customers to implement their suggested security best practices to minimize the risk of vulnerability.
  7. Mitigation from the vendor CISA ICSA-23-264-05 · 1 productSecurity Best Practices

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

CISA Known Exploited Vulnerability

Date Added
2021-11-03
Patch Due Date
2022-05-03
Ransomware Use
Unknown
Required Action
Apply updates per vendor instructions.

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2021-01-08
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-x7fx-mcc9-27j7

Frequently asked questions

What is CVE-2020-16013?

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.

Is CVE-2020-16013 actively exploited?

Yes. CVE-2020-16013 is on the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning it has been confirmed as actively exploited in the wild. CISA requires federal agencies to patch by 2022-05-03.

What is the CVSS score for CVE-2020-16013?

CVE-2020-16013 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Running chromium-browser? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record