News for hackers. Stuff that matters.
Re:Show HN: Firefox in WebAssembly by yjftsjthsd-h on Wednesday July 15, 2026 @06:42PM (#48928131)
In mean... It kinda feels like this is legitimately true? An attacker trying to do anything on a user's machine through this would have to find a Firefox vulnerability and a vulnerability in the wasm runtime, which is such a high bar that I would actually feel remarkably safe running this thing. The only question is how performance works and whether there are any pain points using as a daily driver, but those feel likely to be a pretty minor point. Oh, and the usual caveat that an attacker can still compromise things inside the sandbox which does leave a certain amount of exposure (but if you run different things in different instances they're isolated).
Re:Show HN: Firefox in WebAssembly by rlmineing_dead on Wednesday July 15, 2026 @07:03PM (#48928344)
This is true but also this is probably also only half true. Sandboxing is not a fully solved issue since this 100% degrades firefox sandboxing since fission cant run and its running in singleprocess mode. Just wanted to be honest about this
Re:Show HN: Firefox in WebAssembly by Retr0id on Wednesday July 15, 2026 @09:05PM (#48929263)
Assuming you're running Firefox as the outer browser too, in theory it only needs a single bug in the wasm runtime, plus a sandbox escape.
Re:Show HN: Firefox in WebAssembly by coolelectronics on Wednesday July 15, 2026 @10:18PM (#48929664)
Unless you're running every origin in a different instance, I wouldn't use this as a daily driver, since a site would only need to find a renderer vuln to be able to read the rest of your cookies as multiprocess isolation is disabled here
Re:Show HN: Firefox in WebAssembly by one33seven on Thursday July 16, 2026 @02:24AM (#48930973)
You are forgetting that this is largely edited by AI as a fun project. Finding a bug in that firefox probably is a lot easier than usual.