CVE-2026-32064 is a missing authentication flaw in OpenClaw's sandbox browser, scored 7.7 by NVD. The noVNC observer ran x11vnc with no password, so anything that could reach the port could watch or control the browser. Upgrade to 2026.2.21, rebuild and recreate containers.
What's affected
OpenClaw 2026.2.19-2 and earlier. The patched version is 2026.2.21.
The advisory says the runtime already published the port on the host loopback interface only, so the exposure is to other local users and processes on the host, unless you published the port wider.
The fix needs a rebuilt sandbox browser image and recreated containers. The advisory says existing containers will not pick it up on their own.
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.
- Rebuild the sandbox browser image and recreate browser containers.
- Check that no sandbox browser container publishes its noVNC port on a non-loopback interface. The new audit checks flag this.
- Restrict who has shell access on the host.
Why it matters
The record lists CWE-306, missing authentication for a critical function. The x11vnc server was started with the no password option. The fix requires VNC password authentication, generates a password for each container and uses short lived token URLs for observer links.
Loopback only binding limits exposure but is not authentication. On a shared host, any local user can connect to a loopback port.
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
Is this reachable from the internet?
Per the advisory, the port was published on loopback. It becomes more exposed if you changed that.
Sources
Last reviewed: 19 October 2026.
