Considering that JS is JIT'd (and V8 has had JS based RCEs in the past), is there any reason to believe webasm is a significant security hole?
window.AudioContext = undefined
saved me from 2 previous Chrome RCEs.https://www.infoq.com/news/2019/10/WebAssembly-wasm-maliciou...
It's probably tolerable to turn it off for now unless you know you need it.
Using WASM is the method de'jour for turning arbitrary read/write/object leak into RCE. Without WASM, the writer would have to use ROP/etc, but the primitives are still there.
Check out this discussion by a bunch of the big names in the field, including Niklas B who was on the team that originally found this bug: https://twitter.com/spoofyroot/status/1379911787282243584