Loading vulnerability…
CVE-2026-3542 is a high-severity vulnerability in Google Chrome's WebAssembly handling, specifically in V8's AsmJS-to-WebAssembly translation pipeline prior to Chrome 145.0.7632.159. The flaw stems from incorrect state management while processing heap access expressions in AsmJS modules. Parser state used to track shift-expression metadata is stored in shared parser instance fields and can be overwritten during recursive parsing of nested shift expressions. When the parser later truncates and rewrites the generated WebAssembly opcode stream based on this stale state, it can corrupt the emitted bytecode and misalign instruction boundaries. As a result, bytes originally emitted as immediates can be reinterpreted as WebAssembly opcodes. Because AsmJS-generated WebAssembly is treated as trusted during instantiation, normal decoder validation paths may be skipped, allowing malformed but accepted opcode streams to reach execution. This can lead to out-of-bounds memory access and forms the basis for more advanced exploitation.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Chrome/V8 AsmJS state-management flaw that corrupts the generated WebAssembly opcode stream, enabling execution of unvalidated WebAssembly opcodes and potentially arbitrary read/write and arbitrary code execution outside the Ubercage sandbox.
High-severity vulnerability in Google Chrome WebAssembly due to 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.