Skip to content

Security: browser-gateway/browserserve

Security

SECURITY.md

Security Policy

Reporting a vulnerability

Please report security vulnerabilities privately. Do not open a public issue for a security report.

Include a description, reproduction steps, affected versions, and any known impact. We aim to acknowledge reports within a few business days.

Scope

browserserve runs untrusted web content in Chromium on your infrastructure. Notes relevant to a secure deployment:

  • Run the container with the shipped docker/seccomp.json so Chromium's sandbox stays enabled. Without it, sessions fail closed rather than silently dropping the sandbox.
  • The runtime performs all real work as a non-root user (uid 999). It starts as root only to self-delegate a cgroup slice when the host allows it, then drops privileges.
  • Session isolation is process- and directory-per-session; where the host permits, per-session cgroup memory caps and atomic tree-kill are added. Run browserserve doctor to see the active isolation tier.

Pre-release software: security guarantees are not final until a 1.0 release.

There aren't any published security advisories