Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2020-16040: Insufficient data validation in Google Chrome V8

Published Jan 8, 2021 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3.1
EPSS99.6%100th percentile
CISA KEVNoNot listed
In the wildReported4 exploitation records in Mallory
Vendor
Google
IdentifiersCVE-2020-16040CWE-20 · Improper Input Validation

CVE-2020-16040 is a high-severity vulnerability in the V8 JavaScript engine in Google Chrome prior to version 87.0.4280.88. The flaw is described as insufficient data validation in V8 that can be triggered by a crafted HTML page. Successful exploitation can lead to heap corruption in the browser process. The issue was reported by Lucas Pinheiro of Microsoft Browser Vulnerability Research on 2020-11-19 and was later observed being used in the wild as part of malicious delivery chains.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can corrupt heap memory in the Chrome process and may enable remote code execution in the context of the browser. In practical attack chains, the vulnerability can be used to compromise a visiting user through web content, potentially allowing execution of attacker-controlled code, follow-on malware delivery, and further intrusion activity subject to Chrome sandbox and post-exploitation constraints.

Mitigation

If you can’t patch tonight, do this now.

Until patching is complete, reduce exposure by limiting use of untrusted or attacker-controlled websites, restricting browser use on high-risk systems, and enforcing application isolation and least-privilege controls. Enterprise defenders can also harden browser deployment through rapid update enforcement, web filtering, exploit protection, and monitoring for suspicious browser-child-process behavior or anomalous post-browser execution. These measures do not replace patching.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 87.0.4280.88 or later. Apply the vendor-provided security update across all affected systems and ensure Chromium-based deployments that inherit the vulnerable V8 version are reviewed and updated as appropriate. Standard patch-management validation should confirm that the browser version in use is no longer prior to 87.0.4280.88.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication
FAQ

Frequently asked questions

Is CVE-2020-16040 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2020-16040?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2020-16040, the earliest disclosed Nov 19, 2020.
Is there a patch for CVE-2020-16040?
Upgrade Google Chrome to version 87.0.4280.88 or later. Apply the vendor-provided security update across all affected systems and ensure Chromium-based deployments that inherit the vulnerable V8 version are reviewed and updated as appropriate.
What products are affected by CVE-2020-16040?
Google Chrome.
How severe is CVE-2020-16040?
CVE-2020-16040 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 99.6% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+5 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence5Every report linking this CVE to a named adversary.
Associated malware9Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.