CVE-2026-4457 is a high-severity type confusion vulnerability in the V8 JavaScript engine used by Google Chrome. In Chrome versions prior to 146.0.7680.153, a remote attacker could trigger heap corruption by causing V8 to mis-handle object types while processing crafted web content. Available reporting associates the issue with WebAssembly GC object handling and describes a confused write condition involving Wasm struct operations. Type confusion in this context can cause the engine to treat one object representation as another incompatible type, leading to invalid memory access and heap corruption during JavaScript or WebAssembly execution initiated from a malicious HTML page.
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.
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.