Loading vulnerability…
CVE-2020-16040 is a high-severity vulnerability in the V8 JavaScript engine in Google Chrome caused by insufficient data validation. According to the provided content, affected Chrome versions prior to 87.0.4280.88 could be induced into heap corruption by a remote attacker via a crafted HTML page. The issue was reported by Lucas Pinheiro of Microsoft Browser Vulnerability Research on 2020-11-19 and patched in Chrome 87.0.4280.88. The available content does not identify the exact vulnerable V8 function or code path.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit module targeting CVE-2020-16040, an integer overflow vulnerability in Google Chrome's V8 engine (SimplifiedLowering phase) affecting versions before 87.0.4280.88 (64-bit). The exploit is delivered via a malicious HTTP server that serves a crafted HTML/JavaScript payload to the victim's browser. The JavaScript leverages the vulnerability to achieve arbitrary read/write in memory, then uses WebAssembly to allocate RWX memory, copies attacker-supplied shellcode into it, and executes it. The exploit requires the browser to be run with the --no-sandbox flag, which is not the default configuration. The module supports exploitation on Linux, Windows 10, and macOS platforms. The only fingerprintable endpoint is the root path (/) of the HTTP server started by the Metasploit module. The repository is structured as a single Ruby file containing the exploit logic, with embedded JavaScript for the browser-side payload. The exploit is operational and allows for arbitrary code execution in the context of the Chrome renderer process.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Google Chrome V8 vulnerability (CVE-2020-16040) referenced as being leveraged in China-aligned campaigns alongside social engineering (fake Chrome update lures) and follow-on payload delivery.
A Google Chrome vulnerability described as an insufficient data validation flaw, leveraged in the SHADOW-EARTH-045 campaign alongside social engineering to facilitate malware execution.
A Google Chrome vulnerability referenced as being exploited via a PeckBirdy-hosted script in a watering-hole style campaign to compromise visitors and facilitate follow-on malware delivery.
A remote code execution (RCE) vulnerability in Google Chrome that was leveraged as an exploit in the Shadow-Void-044 campaign to help deliver/execute attacker code and support persistent access operations.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.