dbcve.org
OpenclawApplication

CVE-2026-62195

HIGH · 8.3 CVSS v3.1 Published 2026-07-13
Fix available
A fix is available. Upgrade to 2026.6.6 or later.
See remediation →
89/100
Remediation priority · High
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 versions 2026.5.20 before 2026.6.6 contain an authorization bypass vulnerability in the MCP loopback feature that allows lower-trust callers to execute owner-only tools. Attackers can bypass authorization checks through configured input paths to execute or persist actions beyond their intended permissions.

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 versions 2026.5.20 through 2026.6.5 contain an authorization bypass in the MCP loopback feature where lower-privilege callers can execute owner-restricted tools by manipulating configured input paths to circumvent authorization checks, allowing unauthorized execution or persistence of privileged actions.

MitigationUpdate OpenClaw to version 2026.6.6 or later which contains the fix for the authorization bypass in the MCP loopback feature.

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.5.20, < 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
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

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

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. Determine installed OpenClaw version
    Run 'openclaw --version' or check the package manifest/config file for the installed OpenClaw version number
    Affected if version is >= 2026.5.20 and < 2026.6.6
  2. Identify if MCP loopback feature is configured
    Examine the OpenClaw configuration files (typically in /etc/openclaw/ or ~/.openclaw/) for any 'mcp', 'loopback', or similar MCP-related settings
    Affected if MCP loopback feature is enabled in the configuration
  3. Review configured input paths for MCP loopback
    Inspect the MCP loopback configuration entries to identify any input path settings that could be manipulated by lower-privilege callers
    Affected if MCP loopback is configured with user-controllable input path parameters
  4. Check for unexpected privileged tool executions
    Review OpenClaw audit logs or execution history for tool invocations that occurred via the MCP loopback interface from lower-privilege sessions
    Affected if privileged tools were executed through MCP loopback by non-owner callers

You are affected if OpenClaw version is between 2026.5.20 and 2026.6.5 inclusive AND the MCP loopback feature is enabled with configurable input paths that could be manipulated by lower-privilege users.

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

Update OpenClaw to version 2026.6.6 or later which contains the fix for the authorization bypass in the MCP loopback feature.

Recommended fix High confidence

2026.6.6

  1. 1. Identify the current installed version of OpenClaw by checking the application or configuration files
  2. 2. Stop any running OpenClaw services or processes
  3. 3. Upgrade OpenClaw to version 2026.6.6 or later using the package manager or build system used in your deployment (e.g., pip install openclaw==2026.6.6, docker pull openclaw:2026.6.6, or compile from source at the 2026.6.6 tag)
  4. 4. Verify the upgrade was successful by checking the installed version matches 2026.6.6 or later
  5. 5. Restart OpenClaw services
  6. 6. Test that the MCP loopback feature now correctly enforces authorization checks for lower-trust callers

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-62195 — 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-62195 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