Policy Bypass in OpenClaw via Blocked WebSocket URLs

Executive Summary

CVE-2026-62197 is a policy bypass vulnerability in OpenClaw versions before 2026.6.6. The issue occurs in the browser CDP (Chrome DevTools Protocol) discovery feature, which incorrectly accepts blocked WebSocket URLs.

This flaw allows attackers with lower-trust access to bypass OpenClaw's policy restrictions and reach network destinations that should have been blocked. The vulnerability is classified under CWE-284 (Improper Access Control) and CWE-918 (Server-Side Request Forgery).

• Affected versions: OpenClaw >= 0 and < 2026.6.6.
• Severity: High (CVSS v3.1 BaseScore=8.5, CVSS v4.0 BaseScore=6.3).
• Mitigation: Upgrade to OpenClaw version 2026.6.6 or later, restrict the feature to trusted operators, or disable it when unnecessary.

Useful 0 Not Useful 0

Detection Guidance

Detecting this vulnerability requires checking if your system is running an affected version of OpenClaw (versions prior to 2026.6.6) and verifying if the browser CDP discovery feature is enabled and exposed to untrusted input.

• Check the installed version of OpenClaw. If you are using npm, run: npm list openclaw. Look for versions earlier than 2026.6.6.
• Inspect OpenClaw configuration files or environment variables to determine if the browser CDP discovery feature is enabled. This may involve reviewing settings related to WebSocket URLs or CDP endpoints.
• Monitor network traffic for unexpected WebSocket connections to blocked or restricted destinations. Tools like Wireshark or tcpdump can help identify suspicious WebSocket traffic patterns.
• Review access logs for OpenClaw to identify any unauthorized or lower-trust access attempts to network destinations that should be restricted.

Since the vulnerability involves policy bypass via WebSocket URLs, there are no direct commands to detect exploitation, but these steps can help identify vulnerable configurations or suspicious activity.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can impact you if you use OpenClaw versions before 2026.6.6 and have the browser CDP discovery feature enabled.

• Attackers with lower-privilege access could bypass OpenClaw's policy restrictions, potentially gaining unauthorized access to network destinations that should have been blocked.
• This could lead to unauthorized data access, network reconnaissance, or further exploitation of internal systems, depending on the attacker's goals.
• The high CVSS score (8.5) indicates a significant risk, particularly due to the potential for high confidentiality impact and the low complexity of exploitation.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability could affect compliance with standards and regulations that require strict access controls and protection of sensitive data.

• GDPR: If the vulnerability leads to unauthorized access to personal data, it could result in a breach of GDPR's data protection requirements, potentially leading to fines or legal action.
• HIPAA: For organizations handling protected health information (PHI), unauthorized access due to this vulnerability could violate HIPAA's Security Rule, which mandates safeguards for electronic PHI.
• Other standards like PCI DSS (for payment data) or industry-specific regulations may also be impacted if the vulnerability allows access to restricted systems or data.

Failure to mitigate this vulnerability could result in non-compliance, regulatory penalties, or reputational damage.

Useful 0 Not Useful 0

Mitigation Strategies

• Upgrade OpenClaw to version 2026.6.6 or later immediately. This is the most effective mitigation as it includes the patch for the vulnerability.
• If upgrading is not immediately possible, restrict the browser CDP discovery feature to trusted operators only. Disable it entirely if it is not necessary for your use case.
• Review and enforce strict access controls to ensure that only trusted users or systems can interact with OpenClaw, particularly the CDP discovery feature.
• Monitor network traffic and logs for any signs of exploitation, such as unexpected WebSocket connections to blocked destinations.
• Apply network-level restrictions to block WebSocket connections to unauthorized or high-risk destinations, even if OpenClaw policy should already enforce this.

Useful 0 Not Useful 0