SECURITY • OpenClaw quick fix
Featured: @lyrie_ai
Self-hosted OpenClaw older than 2026.4.10? Audit it now.
Recent CVE chatter is worth acting on if you expose OpenClaw beyond your laptop. GitHub, NVD, and CVE records now point to several fixed-before-2026.4.10 issues: sandbox noVNC helper-route authentication bypass, Nostr plugin profile-route access control, sandbox browser CDP relay binding too broadly to `0.0.0.0`, and external hook metadata being enqueued as trusted system events. Treat this as an upgrade-and-exposure audit, not a panic reinstall.
In simple words: Make a safe copy if the step could change your setup, try the smallest check, then confirm OpenClaw is back to normal before doing more. The source link and commands stay below for people who want the technical detail.
Checklist
Check the running OpenClaw version on every laptop, VPS, and shared agent box — especially anything reachable over a network.
Fast local version and backup check
openclaw --version
openclaw backup create --verify
If any install is older than 2026.4.10, upgrade before continuing normal shared-channel, hook, browser-sandbox, or plugin work.
Review whether sandbox/noVNC routes, browser/CDP relay ports, Nostr plugin profile routes, or hook/webhook ingress were ever exposed to other users, tunnels, reverse proxies, or public hosts.
Exposure questions to answer before trusting the host again
- Was any sandbox browser/noVNC/CDP route reachable outside localhost or a trusted VPN?
- Was hook/webhook ingress reachable from untrusted senders?
- Were tunnels, reverse proxies, shared ports, or public VPS firewall rules open during the vulnerable window?
- Do logs show unexpected browser sessions, hook names, profile-route access, or agent actions?
If a DevTools/CDP endpoint or hook ingress was externally reachable, treat it as incident-response territory: preserve logs, isolate the host, rotate affected secrets, and compare state against a known-good backup.
After upgrading, run a known-good smoke test and remove any temporary tunnel/proxy rules you do not still need.
Snapshot first if this is a production-like operator setup: verified backup, upgrade, smoke test, then keep the rollback note with the incident/audit record.
Success looks like
• No exposed/shared install remains below 2026.4.10.
• You know whether noVNC/sandbox, CDP relay, Nostr plugin, or hook ingress surfaces were reachable from outside the trusted operator machine.
• The upgraded install passes a simple gateway/channel/browser-smoke test before agents are trusted again.
• Any externally reachable DevTools or hook surface has an incident note, log review, and secret-rotation decision attached.
Source: GitHub advisories + CVE/NVD records · link