On 64-bit systems with virtual address space to spare, you can offload bounds checking to MMU by memory mapping 2 GB+ protection zone both below and above the exposed memory region.
If you then limit all pointers/offsets to 32-bit, there should be no direct way to corrupt anything else. You can't reach anything interesting within 32-bit offsets. Of course one can corrupt WebAssembly instance memory all they want, but it won't matter.
Performance and security win.
Left CPU bugs outside consideration, hopefully those can be addressed in WASM codegen. Not like it's that different from current Javascript JIT cases.
You can't overwrite code or the true call stack, so what's the (security) risk?
For a very extreme convoluted example, maybe that value given back to the JavaScript layer will trigger a patient death by sending the wrong value to their insulin device monitor.
But yeah, code and true call stack will be perfectly safe.
It's just a matter of time.
* Or any other device with data corrupting hardware or software issues.
Successful lawsuits against insecure software need to become a common event until most companies actually start paying attention to their technology stack and development processes.
The goal of software security is to minimize all attack vectors.
Logic bugs < Logic bugs + Memory corruption bugs