openclaw could start the sandbox browser bridge server without authentication.
When the sandboxed browser is enabled, openclaw runs a local (loopback) HTTP bridge that exposes browser control endpoints (for example /profiles, /tabs, /tabs/open, /agent/*). Due to missing auth wiring in the sandbox initialization path, that bridge server accepted requests without requiring gateway auth.
A local attacker (any process on the same machine) could access the bridge server port and:
This is a localhost-only exposure (CVSS AV:L), but provides full browser-session compromise for sandboxed browser usage.
2026.1.29-beta.1 (first npm release that shipped the sandbox browser bridge)>=2026.1.29-beta.1 <2026.2.142026.2.142026.2.14 (recommended).agents.defaults.sandbox.browser.enabled=false).Fix commits:
Thanks to Adnan Jakati (@jackhax) of Praetorian for reporting this issue.
{
"cwe_ids": [
"CWE-306"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-18T17:45:31Z",
"nvd_published_at": null,
"severity": "HIGH"
}