OpenClaw: Browser debug/export routes could reuse already-open blocked tabs
Affects openclawSource GCVE Database
CVSS 6.5 Medium : upgrade to 2026.4.29 when convenient.
Data as of 2 Jul 2026, 23:20 UTC
- Patch
- Available – fixed in 2026.4.29
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:NWhat to do
Upgrade openclaw to 2026.4.29.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmopenclaw | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in OpenClaw version 2026.4.29. Until upgrading, operators should close blocked tabs before using the debug/export features and restrict access to browser debug routes. Additionally, it is recommended to keep channel and tool allowlists narrow, avoid sharing a Gateway instance between mutually untrusted users, and disable the affected feature when not needed.
Description
OpenClaw versions prior to 2026.4.29 have a vulnerability in browser debug/export routes where already-open blocked tabs could be reused without reapplying the expected SSRF policy. This allows an attacker with access to these routes to potentially export or inspect content from tabs that should be protected by browser network policies. The vulnerability affects the specific feature and configuration related to browser debug/export routes and does not alter the trusted-operator model of OpenClaw. The issue is mitigated by closing blocked tabs before using debug/export features and restricting access to these routes until patched.