Loading vulnerability…
CVE-2026-4447 is a high-severity vulnerability in the V8 JavaScript engine in Google Chrome prior to 146.0.7680.153. The flaw is rooted in an inappropriate implementation in the Maglev JIT compiler's Phi untagging logic. In the described vulnerable path, Maglev can untag a Phi node to a Float64 representation and later retag it through a Float64ToTagged conversion using canonicalized Smi conversion, while still treating the resulting value as a HeapObject. This can cause the compiler to incorrectly omit a required heap-object check and permit a Smi value to be stored into an object field that optimized code assumes contains only HeapObjects. The resulting type confusion breaks V8 heap invariants and can be leveraged from a crafted HTML page to achieve 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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Chrome/V8 Maglev JIT vulnerability caused by unsafe Phi untagging and incorrect type assumptions, leading to Smi-to-HeapObject type confusion and exploit primitives.
A high-severity vulnerability in Chrome's V8 JavaScript engine described as inappropriate implementation.
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.