CVE-2026-32064

The sandbox browser entrypoint launched x11vnc without authentication (-nopw) for noVNC observer sessions.

OpenClaw-managed runtime flow publishes the noVNC port to host loopback only (127.0.0.1), so default exposure is local to the host unless operators explicitly expose the port more broadly (or run the image standalone with broad port publishing).

Affected Packages / Versions

• Package: docker/openclaw
• Affected: <= 2026.2.19-2
• Patched: >= 2026.2.21

Technical details

• scripts/sandbox-browser-entrypoint.sh used x11vnc ... -nopw for noVNC observer flow.
• websockify exposed noVNC for the container listener.
• OpenClaw runtime (src/agents/sandbox/browser.ts) already mapped host publish to loopback, but observer auth was missing.

Fix Commit(s)

• 621d8e1312482f122f18c43c72c67211b141da01
• 8c1518f0f3e0533593cd2dec3a46c9b746753661

Release Process Note

Patched version is pre-set to the planned next release (2026.2.21). After npm release, this advisory can be published without further field edits.

OpenClaw thanks @TerminalsandCoffee for reporting.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2026-32064 has a CVSS score of 7.7 (High). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.21); upgrading removes the vulnerable code path.

Kodem intelligence

• Require VNC password auth in the sandbox browser entrypoint (x11vnc -rfbauth), replacing -nopw.
• Generate per-container noVNC password in runtime and inject OPENCLAW_BROWSER_NOVNC_PASSWORD.
• Emit short-lived noVNC observer token URLs instead of sharing raw noVNC passwords in shared URLs.
• Keep loopback-only host port publish and bump sandbox browser security hash epoch.
• Add security audit findings for sandbox browser containers that publish ports on non-loopback interfaces.

Operational note: rebuild the sandbox browser image and recreate browser containers so existing containers pick up the fix.

1. What is CVE-2026-32064? CVE-2026-32064 is a high-severity improper authentication vulnerability in openclaw (npm), affecting versions < 2026.2.21. It is fixed in 2026.2.21. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2026-32064? CVE-2026-32064 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-32064? openclaw (npm) versions < 2026.2.21 is affected.
4. Is there a fix for CVE-2026-32064? Yes. CVE-2026-32064 is fixed in 2026.2.21. Upgrade to this version or later.
5. Is CVE-2026-32064 exploitable, and should I be worried? Whether CVE-2026-32064 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-32064 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-32064? Upgrade openclaw to 2026.2.21 or later.