{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiggpx47j3qyskh4wvxwjkanlqdi46pa4uyoj27gn5n2cvgg3llk7q",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mm2xrldgdkw2"
  },
  "path": "/viewtopic.php?t=33437&p=274222#p274222",
  "publishedAt": "2026-05-17T16:38:22.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> You're missing the point. Look up \"sandbox escape\". Compromised content processes can induce crashes in the parent, often by manipulating the very IPC protocol separating the processes (which is N/A in Pale Moon). Unless Dactyloidae has addressed all applicable e10s/IPC bugs (which have been categorically dismissed in our development where not related to plugins and NPAPI), they are vulnerable through that mechanism to a whole host of overflow, UAF and RCE bugs. Hence my note of caution.\n\nWould you say then that Pale Moon is likely to be the safest modern browser for the average user to use, since it completely avoids the vast array of vulnerabilities and exploits available against the multi-process browsers?\n\nFor example, if you were to set up a browser for your dear old aunt, who knows absolutely nothing about browser security issues, and your only concern was that she not trip into some exploit, would you set her up with Pale Moon, Edge, Firefox, Safari, etc?\n\n* * *",
  "title": "Browser Support • Re: Why is Pale Moon so slow?",
  "updatedAt": "2026-05-17T16:38:22.000Z"
}