> WASM can have weaker security within the sandbox because it doesn't have access to some of the more sophisticated mitigation measures that native code does,

> WASM can have weaker security within the sandbox because it doesn't have access to some of the more sophisticated mitigation measures that native code does, And that's mostly read-only data pages. The primary blocker there is how to integrate that capability with ArrayBuffer in the web platform, since Wasm memories can be exposed (or aliased) as ArrayBuffer objects, and most engines aren't prepared to encourage non-writable holes in ArrayBuffers.