Sandbox browser container launched Chromium with --no-sandbox by default, disabling Chromium's OS-level sandbox protections.
openclaw (npm ecosystem)2026.2.19-2<= 2026.2.19-22026.2.21When --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.
--no-sandbox removed from sandbox browser entrypoint.OPENCLAW_BROWSER_NO_SANDBOX / CLAWDBOT_BROWSER_NO_SANDBOX.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.
{
"cwe_ids": [
"CWE-693"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-03T18:10:34Z",
"nvd_published_at": null,
"severity": "MODERATE"
}