CVE-2026-4447 is a high-severity vulnerability in the V8 JavaScript engine in Google Chrome prior to 146.0.7680.153. The issue is described as an inappropriate implementation flaw in V8 that can be triggered by a crafted HTML page. Available reporting associates the bug with a V8 condition in which a Smi value can be written where a HeapObject is expected, creating a potential fake object primitive if type and tag validation can be bypassed. The vulnerability affects Chrome and Chromium-based browsers that incorporate the vulnerable V8 version. Successful exploitation is reported to allow arbitrary code execution within the browser sandbox.
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.
No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.