CVE-2026-35673: OpenClaw · Browser debug/export routes could reuse already-open blocked tabs
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 2026.4.29 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- 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:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.4.29.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | 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 patch is available in OpenClaw CLI version 2026.4.29. Until systems are updated, operators should close blocked tabs before using 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 between mutually untrusted users, and disable the affected feature when not needed.
Description
A vulnerability in OpenClaw CLI's browser debug/export routes allows reuse of already-open blocked private-network tabs without enforcing the expected SSRF policy. This could lead to unauthorized export or inspection of content that should be protected by browser network policies. The issue affects versions from 2026.1.29 up to but not including 2026.4.29. A fix is available starting with version 2026.4.29. Mitigations include closing blocked tabs before using debug/export features and restricting access to browser debug routes until patched.