Free AI Safety Workshop — in collaboration with explainx.aiSave your seat
AgentbeamBeta
AI agent vulnerability · OpenClaw

CVE-2026-32046: OpenClaw: Chrome --no-sandbox disabled OS-level browser sandbox in sandbox browser container

mediumCVSS 4.0 4.8GHSA-43x4-g22p-3hrq

Summary Sandbox browser container launched Chromium with --no-sandbox by default, disabling Chromium's OS-level sandbox protections. Affected Packages / Versions - Package: openclaw (npm ecosystem) - Latest published npm version at triage time (2026-02-21): 2026.2.19-2 - Affected range: <= 2026.2.19-2 - Planned patched version for next release: 2026.2.21 Impact When --no-sandbox is enabled by default, renderer…

Published Mar 3, 2026 · Updated Mar 30, 2026

Affected packages

openclaw

Ecosystem
npm
Affected
< 2026.2.21
Fixed in
2026.2.21
Check
npm ls openclaw

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Summary

Sandbox browser container launched Chromium with --no-sandbox by default, disabling Chromium's OS-level sandbox protections.

Affected Packages / Versions

  • Package: openclaw (npm ecosystem)
  • Latest published npm version at triage time (2026-02-21): 2026.2.19-2
  • Affected range: <= 2026.2.19-2
  • Planned patched version for next release: 2026.2.21

Impact

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

  • Default --no-sandbox removed from sandbox browser entrypoint.
  • Explicit opt-in added via OPENCLAW_BROWSER_NO_SANDBOX / CLAWDBOT_BROWSER_NO_SANDBOX.
  • Browser container hash migration + security audit checks added so stale containers are surfaced and can be recreated safely.

Fix Commit(s)

  • e7eba01efc4c3c400e9cfd3ce3d661cbc788a631
  • 1835dec2004fe7a62c6a7ba46b8485f124ec6199

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.

Credited to TerminalsandCoffee.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More OpenClaw vulnerabilities

All OpenClaw entries