> Of course Safari already has the same risk Which is the reason the JIT runs in its own sandbox connected through IPC IIRC. Breaking the JIT isn’t supposed t

> Of course Safari already has the same risk Which is the reason the JIT runs in its own sandbox connected through IPC IIRC. Breaking the JIT isn’t supposed to even get you access to the parent process (Safari), let alone anything more, assuming you don’t have a kernel exploit too.