Disclosed weakness · no CVE recorded
OpenClaw browser results could expose connection credentials to the model
OpenClaw · OpenClaw · browser tool
First documented disclosure · Review checkpoint
Summary
Listing or opening browser tabs could include authentication secrets from the browser connection URL.
Severity and exploitation evidence
No CVSS score recorded in this review.
Exploitation not established: The upstream sources document the correction and identify no malicious use.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
Model-facing tab and open results retained authenticated WebSocket URLs after the runtime had established its browser connection.
Conditions required
A loopback browser profile uses HTTP Basic authentication or a query token in its CDP endpoint.
Potential impact
Browser connection credentials could enter model context and any downstream records of the tool result.
Affected versions and configurations
The public report identifies the affected browser path without a complete packaged-version range. The reviewed 2026.11.4 source lacks this output correction.
Fix and mitigation status
2026.11.5.
Practical next steps
Upgrade to 2026.11.5 or later. Review retained browser tool outputs and rotate exposed browser connection credentials where warranted.
Operating lesson
Keep transport credentials inside the component that owns the connection.
Evidence and limits
The first reviewed public report is PR 137756 from September 4. PR 196262 merged November 15 and the stable release shipped November 17. The sources demonstrate the exposure with synthetic credentials and identify no theft.
Sources
- OpenClaw original browser-output credential report
Primary source ·
- OpenClaw merged browser-output correction
Primary source ·
- OpenClaw 2026.11.5 release notes
Primary source ·