CVE-2026-32046 is an insecure default in OpenClaw, scored 5.3 by NVD. The sandbox browser container started Chromium with the OS level sandbox disabled, so a renderer bug no longer needed a separate escape. Upgrade to 2026.2.21 or later and recreate old containers.
What's affected
OpenClaw 2026.2.19-2 and earlier. The patched version is 2026.2.21.
The fix removes the default no-sandbox flag from the sandbox browser entrypoint. Users can opt in again through an explicit environment variable. The release also adds a container hash migration and security audit checks, so old containers are flagged and can be recreated.
How to check if you're exposed
OpenClaw is distributed on npm, so read the installed version.
npm ls openclaw
npm ls -g openclaw
OpenClaw release numbers are date based, so compare the version against the fixed release named above. If you run it in a container, check the image you deploy and rebuild it after updating.
What to do now
- Upgrade OpenClaw to 2026.2.21 or later.
- Recreate sandbox browser containers so they pick up the new entrypoint. The advisory says stale containers are surfaced by the new audit checks.
- Do not set the opt in variable for no-sandbox unless you accept the risk.
- Run the project's security audit and act on its findings.
Why it matters
The record lists CWE-1188, insecure default initialization of a resource. Chromium's OS sandbox is a layer that limits what a compromised renderer can do. With it off, a bug in page rendering is enough to run code in the container.
Containers help, but they are a second layer, not a replacement. Turning off the browser's own sandbox to make it run in a container is a common shortcut that costs real protection.
The record does not flag this CVE as listed in CISA's Known Exploited Vulnerabilities catalog, and no advisory I read says it is exploited in the wild. Treat it as a patch to schedule promptly, not a fire drill, unless your own logs say otherwise.
Quick check
Does upgrading fix existing containers?
The advisory says to recreate them. The new audit checks are designed to surface stale ones.
Is Chromium itself vulnerable?
No. The issue is the OpenClaw container configuration.
Sources
Last reviewed: 19 October 2026.
