CVE-2026-32046
published 2026-03-21CVE-2026-32046: OpenClaw versions prior to 2026.2.21 contain an improper sandbox configuration vulnerability that allows attackers to execute arbitrary code by exploiting…
PriorityP263critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.29%
20.4th percentile
OpenClaw versions prior to 2026.2.21 contain an improper sandbox configuration vulnerability that allows attackers to execute arbitrary code by exploiting renderer-side vulnerabilities without requiring a sandbox escape. Attackers can leverage the disabled OS-level sandbox protections in the Chromium browser container to achieve code execution on the host system.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| openclaw | openclaw | < 2026.2.21 | 2026.2.21 |
| openclaw | openclaw | >= 0 < 2026.2.21 | 2026.2.21 |
Detection & IOCsextracted from sources · hover to see the quote
- →Look for OpenClaw (formerly Moltbot or Clawdbot) processes running without OS-level sandbox protections enabled in the Chromium browser container, which may indicate exploitation of this misconfiguration. ↗
- →Flag OpenClaw versions prior to 2026.2.21 in asset inventory; these versions are vulnerable to renderer-side code execution without requiring a sandbox escape. ↗
- ·The vulnerability stems from disabled OS-level sandbox protections in the Chromium browser container bundled with OpenClaw. No sandbox escape is required — renderer-side exploitation is sufficient for host code execution. ↗
- ·OpenClaw is also tracked under its former names Moltbot and Clawdbot; ensure detection and asset inventory rules cover all three product names. ↗
CVSS provenance
nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv4.04.8MEDIUMCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
OpenClaw: Chrome --no-sandbox disabled OS-level browser sandbox in sandbox browser container
ghsa·2026-03-03
CVE-2026-32046 [MEDIUM] CWE-693 OpenClaw: Chrome --no-sandbox disabled OS-level browser sandbox in sandbox browser container
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
- 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_BROWSE
OSV
OpenClaw: Chrome --no-sandbox disabled OS-level browser sandbox in sandbox browser container
osv·2026-03-03
CVE-2026-32046 [MEDIUM] OpenClaw: Chrome --no-sandbox disabled OS-level browser sandbox in sandbox browser container
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
- 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_BROWSE
No detection rules found.
No public exploits indexed.
https://github.com/openclaw/openclaw/commit/1835dec2004fe7a62c6a7ba46b8485f124ec6199https://github.com/openclaw/openclaw/commit/e7eba01efc4c3c400e9cfd3ce3d661cbc788a631https://github.com/openclaw/openclaw/security/advisories/GHSA-43x4-g22p-3hrqhttps://www.vulncheck.com/advisories/openclaw-os-level-sandbox-bypass-via-no-sandbox-flag
2026-03-21
Published