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).
docker/openclaw<= 2026.2.19-2>= 2026.2.21scripts/sandbox-browser-entrypoint.sh used x11vnc ... -nopw for noVNC observer flow.websockify exposed noVNC for the container listener.src/agents/sandbox/browser.ts) already mapped host publish to loopback, but observer auth was missing.x11vnc -rfbauth), replacing -nopw.OPENCLAW_BROWSER_NOVNC_PASSWORD.Operational note: rebuild the sandbox browser image and recreate browser containers so existing containers pick up the fix.
621d8e1312482f122f18c43c72c67211b141da018c1518f0f3e0533593cd2dec3a46c9b746753661Patched 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.
{
"severity": "HIGH",
"cwe_ids": [
"CWE-287",
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-03T19:17:48Z",
"nvd_published_at": null
}