CVE-2026-6363 is a type confusion vulnerability in the V8 JavaScript engine used by Google Chrome. It affects Google Chrome versions prior to 147.0.7727.101 and can be triggered when a user is induced to load a crafted HTML page containing malicious JavaScript. The flaw arises from incorrect type assumptions during V8's optimization pipeline, where optimized code may later process an object using an incompatible memory layout. This can cause the renderer process to access memory at incorrect offsets, resulting in out-of-bounds memory access. Reported consequences include out-of-bounds reads, potential out-of-bounds writes, memory corruption, information disclosure, and renderer crashes. The issue is classified as CWE-843.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A type confusion vulnerability in the V8 engine of Google Chrome that could allow a remote attacker to potentially trigger out-of-bounds memory access via a crafted HTML page.
A medium-severity type confusion vulnerability in V8 in Google Chrome.
A type confusion vulnerability in Google Chrome's V8 JavaScript engine that can lead to out-of-bounds memory access when a user visits a crafted web page, with potential for information disclosure, memory corruption, and possible arbitrary code execution within the renderer sandbox.
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.