openclaw
Affected
- introduced
2026.1.29-beta.1, fixed2026.2.14(semver)
Fixed versions
2026.2.14
Fix
- Fixed version
2026.2.14npm install [email protected]
Advisory
Also known as: CVE-2026-28468
OpenClaw has an authentication bypass in sandbox browser bridge server
Summary
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.
Impact
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.
Affected Versions
2026.1.29-beta.1 (first npm release that shipped the sandbox browser bridge)>=2026.1.29-beta.1 <2026.2.14Patched Versions
2026.2.14Mitigation
2026.2.14 (recommended).agents.defaults.sandbox.browser.enabled=false).Fix Details
Fix commits:
Credits
Thanks to Adnan Jakati (@jackhax) of Praetorian for reporting this issue.
High Basis: The source's own band: HIGH
2026.1.29-beta.1, fixed 2026.2.14 (semver)2026.2.14
2026.2.14npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0