CVE-2026-32046: OpenClaw · Chrome --no-sandbox disabled OS-level browser sandbox in sandbox browser container
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 4.8 Medium : upgrade to 2026.7.1 when convenient.
Data as of 19 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.7.1
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.7.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and planned for OpenClaw version 2026.2.21 that removes the default --no-sandbox flag and requires explicit opt-in to disable sandboxing. Users should upgrade to this version once released. The update also includes browser container hash migration and security audit checks to detect and safely recreate stale containers. If you cannot patch yet, users should avoid running the sandbox browser container with the --no-sandbox flag enabled by default.
Description
The OpenClaw CLI sandbox browser container launched Chromium with the --no-sandbox flag enabled by default, disabling Chromium's OS-level sandbox protections. This configuration weakens the isolation of the browser container and increases the potential impact of renderer-side vulnerabilities. The issue affects openclaw npm package versions up to and including 2026.2.19-2. A fix is planned for version 2026.2.21, which removes the default --no-sandbox flag and adds an explicit opt-in mechanism. Additional security measures include browser container hash migration and security audit checks to ensure stale containers are detected and safely recreated.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-43x4-g22p-3hrq (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-32046 (opens in a new tab)
- github.com/openclaw/openclaw/commit/1835dec2004fe7a62c6a7ba46b8485f124ec6199 (opens in a new tab)
- github.com/openclaw/openclaw/commit/e7eba01efc4c3c400e9cfd3ce3d661cbc788a631 (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- vulncheck.com/advisories/openclaw-os-level-sandbox-bypass-via-no-sandbox-flag (opens in a new tab)