Technical Details and Exploit Released for Chrome Remote Code Execution Flaw
## Cybersecurity: Google Chrome WebAssembly Vulnerability
Cybersecurity: Google Chrome WebAssembly Vulnerability
A remote code execution vulnerability affecting Google Chrome's WebAssembly engine has been disclosed, including a fully functional exploit.
The issue originates from a regression in the canonicalization logic for indexed reference types in WebAssembly, identified during TyphoonPWN 2025. This regression allows attackers to craft a hash collision, leading to a bypass of the sandbox via JavaScript Promise Integration (JSPI).
Researchers from SSD Secure Disclosure demonstrated that exploiting a nullability confusion bug, combined with a hash collision technique, provides arbitrary read/write access within the V8 sandbox, enabling native code execution. Seunghyun Lee (0x10n) identified this flaw, securing first place in the Chrome RCE category.
A remote code execution vulnerability affecting Google Chrome's WebAssembly engine has been disclosed, including a fully functional exploit.
Hash Collision Generation: A WebAssembly module builder is used to define recursive type groups with nullability variations, resulting in a candidate collision through a birthday attack. Null-to-Non-Null Cast: The collision allows recasting a null reference as non-null, enabling controlled memory access. Caged Read/Write Primitive: Mapping a controlled object to a WasmArray provides arbitrary offset read/write access within the sandbox. JSPI Sandbox Bypass: By triggering nested WebAssembly.promising calls, the exploit gains stack control, allowing execution of arbitrary native commands. Delivery: Serving the exploit over a local HTTP server and launching Chrome with the --no-sandbox flag facilitates code execution.
This issue affects Chrome stable builds from M135 to M137 for null-equivalence checks and M137+ for JSPI bypass. Google has issued a patch to address these vulnerabilities by reverting flawed logic and enhancing stack-state checks.
Immediate Update: Apply the latest Chrome update from October 2025 or later for the necessary fixes. Avoid --no-sandbox: Do not run Chrome with this flag unless required for debugging purposes. Defense in Depth: Use endpoint protection solutions to monitor unusual WebAssembly activity and process behavior. Audit WebAssembly Usage: Review WebAssembly modules for potential untrusted code execution paths.
Based on reporting by GBHackers.
