openclaw
Affected
- introduced
0, fixed2026.2.21(semver)
Fixed versions
2026.2.21
Fix
- Fixed version
2026.2.21npm install [email protected]
Advisory
Also known as: CVE-2026-32046
OpenClaw: Chrome --no-sandbox disabled OS-level browser sandbox in sandbox browser container
Summary
Sandbox browser container launched Chromium with --no-sandbox by default, disabling Chromium's OS-level sandbox protections.
Affected Packages / Versions
openclaw (npm ecosystem)2026.2.19-2<= 2026.2.19-22026.2.21Impact
When --no-sandbox is enabled by default, renderer compromise no longer requires a separate sandbox escape. This weakens container browser isolation and increases impact from renderer-side bugs.
Resolution
--no-sandbox removed from sandbox browser entrypoint.OPENCLAW_BROWSER_NO_SANDBOX / CLAWDBOT_BROWSER_NO_SANDBOX.Fix Commit(s)
Release Process Note
The advisory patched_versions field is pre-set to the planned next release (2026.2.21). After npm release publication, only advisory publish action should remain.
OpenClaw thanks @TerminalsandCoffee for reporting.
Medium Basis: The source's own band: MODERATE
0, fixed 2026.2.21 (semver)2026.2.21
2026.2.21npm 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