Security
How NEXUS protects you, and how to report a problem responsibly.
How NEXUS is protected
- Sandboxing: web pages run in Chromium’s sandboxed processes, which have very limited access to your files and system. NEXUS never turns the sandbox off.
- Site isolation: different sites run in different processes.
- Up-to-date engine: Chromium 154.0.8037.98 via CEF 154.0.34. Engine updates are the most important security updates, so NEXUS follows CEF’s stable releases.
- Internal pages are isolated: websites can’t open, embed or link to NEXUS’s own pages. Messages from those pages are checked in the main process: who sent them, from which page, and with what values.
- Strict certificates: an invalid HTTPS certificate blocks the page, with no way to click past.
- Downloads: files are marked as downloaded from the internet, so Windows protections apply, and NEXUS asks before opening programs or scripts.
- Signed updates: update information is signed with an Ed25519 key that never leaves the release computer. Installers must match their signed SHA-256 checksum.
- No remote debugging in releases: switches that would let other programs control the browser are removed from release builds.
Reporting a vulnerability
Please report it privately first, through the contact form (choose “bug” and start the subject with “Security”), so it can be fixed before anyone else knows about it. Include the NEXUS version and the steps to reproduce it. Bugs in Chromium itself should go to the Chromium project.
See also security.txt.