dbcve.org
OpenclawApplication

CVE-2026-62197

HIGH · 8.5 CVSS v3.1 Published 2026-07-13
Fix available
A fix is available. Upgrade to 2026.6.6 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OpenClaw before 2026.6.6 contains a policy bypass vulnerability in browser CDP discovery that accepts blocked WebSocket URLs. Attackers with lower-trust access can reach network destinations that should have been blocked by OpenClaw policy when the affected feature is enabled.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

OpenClaw before version 2026.6.6 has a policy bypass in its browser CDP (Chrome DevTools Protocol) discovery mechanism that incorrectly accepts WebSocket URLs that should be blocked by network policy. When the CDP discovery feature is enabled, lower-privilege attackers can circumvent network restrictions and connect to destinations that the policy was intended to block.

MitigationUpgrade to OpenClaw 2026.6.6 or later. If upgrading is not immediately feasible, disable the browser CDP discovery feature if it is not required for operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenclawApplication
Affected:< 2026.6.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed OpenClaw version
    Run the version command for OpenClaw (such as 'openclaw --version' or check the application metadata)
    Affected if The installed version is lower than 2026.6.6
  2. Locate the OpenClaw configuration file
    Find the main configuration file for OpenClaw - typical locations include the application directory, user config folder, or /etc/openclaw/
    Affected if You cannot locate a configuration file to check settings (may indicate default vulnerable state)
  3. Verify CDP discovery feature status
    Inspect the configuration file for a setting related to CDP, Chrome DevTools Protocol, or browser debugging (commonly named 'cdp_discovery', 'devtools_discovery', 'browser_cdp', or similar)
    Affected if The CDP discovery feature is explicitly enabled (set to 'true', 'enabled', '1', or similar)
  4. Review network policy rules for CDP/WebSocket
    Check the network policy or firewall configuration that governs WebSocket or CDP connection destinations - look for rules allowing or blocking specific URL patterns or ports used by CDP
    Affected if Network policy rules exist but do not explicitly block WebSocket URLs in the CDP context, or the policy configuration cannot be verified

You are affected if OpenClaw version is below 2026.6.6 AND the CDP discovery feature is enabled, allowing potential policy bypass of network restrictions on WebSocket connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026.6.6 or later
Fixed in 2026.6.6
Interim mitigation

Upgrade to OpenClaw 2026.6.6 or later. If upgrading is not immediately feasible, disable the browser CDP discovery feature if it is not required for operations.

Recommended fix Moderate confidence

OpenClaw 2026.6.6

  1. 1. Identify the current OpenClaw version by checking the application or configuration files
  2. 2. Download or update to OpenClaw version 2026.6.6 or later from the official repository
  3. 3. Verify the upgrade was successful by checking the version after installation
  4. 4. Test that the CDP discovery feature properly blocks WebSocket URLs according to policy after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openclaw Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-62197 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-62197 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data