The post links to a blog and the most recent post seems to address this concern. (I haven't actually read it yet.) https://microsoftedge.github.io/edgevr/posts

The post links to a blog and the most recent post seems to address this concern. (I haven't actually read it yet.) https://microsoftedge.github.io/edgevr/posts/How-we-are-securing-our-new-PDF-stack/ https://microsoftedge.github.io/edgevr/posts/How-we-are-secu... Edit after reading: What a joke. They are using a better allocator and doing some fuzzing. This is nowhere close to the approach that Chromium uses which is basically running the PDF viewer via WASM.