Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 261/275 feeds/APIs · 469/469 docs · 9/9 advisories · checked 18:30 UTC Customize Public modeDiscuss ChangeIntel on Discord

OpenClaw's andbox browser noVNC observer lacked VNC authentication

Exact source revision recorded 24 Oct 2026 13:17:17 UTC. It does not establish the source's current position. Latest evidence.

osv · GHSA-25gx-x37c-7pph

Published

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 - 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. ## 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.

Source published
3 Mar 2026 19:17:48 UTC
Source modified
30 Mar 2026 14:11:33 UTC
Observed here
24 Oct 2026 13:17:17 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS_V3 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

CVSS_V4 · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Publisher rating · HIGH

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 10 Nov 18:30 UTC · 261 of 275 readable · 260 fully read · documentation 469/469 current