Loading vulnerability…
CVE-2021-38003 affects the V8 JavaScript engine in Google Chrome before version 95.0.4638.69 and applications embedding vulnerable V8 versions. An overflow path in JsonStringifier::SerializeArrayLikeSlow() can return EXCEPTION without setting pending_exception. Subsequent exception handling exposes V8's internal TheHole sentinel to JavaScript. Attackers can misuse this value in JavaScript Map operations to corrupt internal state, obtain out-of-bounds memory access, and ultimately execute arbitrary code in the renderer or embedding process. The vulnerability has been exploited in Chrome-based Android attack chains, malicious Dota 2 custom game modes, and an outdated Chromium component embedded in Sogou Input Method.
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.
This repository contains a working exploit for CVE-2021-38003, a remote code execution vulnerability in the V8 JavaScript engine used by Google Chrome. The structure consists of an HTML file (exp.html) that acts as the main entry point, and two JavaScript files (wps2.js, wps3.js) that implement the exploit logic and payload. The exploit leverages a vulnerability in V8 to achieve arbitrary read/write primitives, then uses WebAssembly to allocate RWX memory and injects x86 shellcode for execution. The shellcode is embedded as a byte array in the JavaScript files. The exploit is operational and demonstrates full code execution in the browser context, requiring the user to open the HTML file in a vulnerable version of Chrome. No external network endpoints or domains are hardcoded; the exploit is self-contained and targets the local browser 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.
19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A known V8-engine vulnerability that UNC3569 exploited in Sogou Input Method's obsolete embedded Chromium 80 component as part of the larger one-click attack chain.
A known V8 vulnerability exploited against Sogou Input Method's embedded Chromium 80 browser as part of the one-click attack chain. The browser's disabled sandbox and web protections enabled host-level code execution, followed by payload retrieval and DLL sideloading to deploy GRAYRABBIT. The article reports that the embedded browser remained outdated and unsandboxed after the Sogou protocol-handler fix.
A JavaScript-engine vulnerability fixed in Chrome 95 in October 2021. Sogou Input Method embedded an outdated Chromium 80 build, enabling UNC3569 to exploit this older flaw as part of the attack chain.
A Google Chrome/V8 JavaScript-engine vulnerability in JSON.stringify that can expose an internal value to JavaScript, enabling memory corruption and arbitrary code execution. It was used as the browser-exploitation stage of the Sogou Input Method attack chain because Sogou embedded an obsolete Chromium 80 build.
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.