Skip to main content
ExploitedIn CISA KEVFix available

CVE-2020-16009

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

  • Published2020-11-03
  • WeaknessCWE-787 · CWE-843

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.183 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Timeline

dates in UTC
  1. 2020-11-0303: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-01-2916:56SSVC exploitation set to activeCISA-ADP

Observed activity

isMalicious corpus · updated 2026-11-04 03: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-16009?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-16009?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Fedoraproject fedora
BranchAffectedFixed in
32.x= 32no fix published
33.x= 33no fix published
Opensuse leap
BranchAffectedFixed in
15.1= 15.1no fix published
15.2= 15.2no fix published
Cefsharp
BranchAffectedFixed in
86.0< 86.0.24186.0.241

5 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.183fixed in 86.0.4240.183custom

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

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.183-bp152.2.26.1
  • chromiumSUSE:Package Hub 15 SP1all versions · fixed in 86.0.4240.183-bp151.3.119.1
  • chromiumSUSE:Package Hub 15 SP1all versions · fixed in 86.0.4240.183-bp151.3.125.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.183-bp151.3.119.1
  • chromiumopenSUSE:Leap 15.1all versions · fixed in 86.0.4240.183-bp151.3.119.1
  • chromiumDebian:14all versions · fixed in 87.0.4280.88-0.1

9 more package ranges on OSV.dev

Vendor advisories

  • CVE-2020-16009 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:4974 Red Hat Product Security14 products fixed

    Red Hat Security Advisory: chromium-browser security update

Full record on NVD

Fix

  1. CISA’s required action: Apply updates per vendor instructions.due 2022-05-03
  2. Vendor fix CISA ICSA-23-264-05 · 1 productRockwell Automation recommends users to update Connected Components Workbench to R21 and later.
  3. Vendor fix Red Hat Product Security RHSA-2020:4974 · 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.
  4. Mitigation from the vendor CISA ICSA-23-264-05 · 1 productCustomers using the affected software are encouraged to apply the risk mitigations, if possible.
  5. 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.
  6. 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
2020-11-03
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-m7mf-48hp-5qmr

Frequently asked questions

What is CVE-2020-16009?

Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.183 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Is CVE-2020-16009 actively exploited?

Yes. CVE-2020-16009 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-16009?

CVE-2020-16009 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 ».

Get alerts for this productCISA KEV additions, November 2021Search CVEs

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

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record