CVE-2026-15776 is a high-severity type confusion vulnerability in the V8 JavaScript engine used by Google Chrome. The issue is described as an inappropriate implementation flaw in V8 that can cause memory corruption by allowing code to treat an object as a different type than intended. In affected Google Chrome versions prior to 150.0.7871.125, a remote attacker can trigger the flaw by delivering crafted HTML content to the browser. Successful exploitation can result in arbitrary code execution within the Chrome 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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
A high-severity type confusion vulnerability in Chrome's V8 engine that can cause memory corruption.
A high-severity type confusion vulnerability in Chrome's V8 engine.
A high-severity remote code execution vulnerability in V8 affecting Google Chrome, allowing arbitrary code execution inside the sandbox via a crafted HTML page.
A high-severity type confusion vulnerability in Chrome's V8 engine.
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.