Cdp

If you’re running OpenClaw with browser control features, you need to patch GHSA-mr32-vwc2-5j6h today. This how-to walks you through the full process: checking your current version, verifying exposure, patching, and applying the new Docker network hardening from 2026.2.21. For the threat model and full vulnerability details, see the news article on GHSA-mr32-vwc2-5j6h. Here we focus on the practical steps. Step 1: Check Your Current Version openclaw --version If you see anything before 2026.2.21-1, you’re vulnerable. The patch was shipped in the -1 suffix release specifically for this CVE — 2026.2.21 alone is not sufficient. ...

If you’re running OpenClaw and haven’t patched to 2026.2.21-1 yet, stop what you’re doing. There’s a high-severity vulnerability — GHSA-mr32-vwc2-5j6h — that you need to know about. What’s the Vulnerability? The flaw lives in OpenClaw’s Browser Relay: specifically, the /cdp WebSocket endpoint that powers browser control features. Prior to the patch, this endpoint had no authentication token requirement. That means any process running locally — or any attacker who can reach your machine — could connect to the CDP WebSocket without proving who they are. ...