dbcve.org
OpenclawApplication

CVE-2026-62194

HIGH · 8.8 CVSS v3.1 Published 2026-07-13
Fix available
A fix is available. Upgrade to 2026.6.9 or later.
See remediation →
94/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 versions 2026.5.20 before 2026.6.9 contain a privilege escalation vulnerability in plugin install commands that allows lower-trust callers to execute or persist actions beyond their intended authorization. Attackers can exploit misconfigured input paths or enabled features to escalate privileges and perform unauthorized actions when the feature is reachable.

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 · high confidence

OpenClaw versions 2026.5.20 through 2026.6.8 contain a privilege escalation vulnerability in the plugin install functionality where insufficient authorization controls allow lower-privileged users to execute plugin install commands beyond their intended permissions. Attackers can exploit misconfigured input path handling or certain enabled features to bypass authorization checks and persist actions with elevated privileges.

MitigationUpgrade to OpenClaw version 2026.6.9 or later to obtain the patched version. Additionally, review and harden plugin install command authorization policies and input path validation until the upgrade can be applied.

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.9

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
High

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

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 applicationAbout/packaging metadata to find the exact version number
    Affected if The version is >= 2026.5.20 and < 2026.6.9
  2. Verify plugin install functionality is present
    Check if the 'plugin install' command or plugin management interface exists in the installation (look for plugin-related binaries, scripts, or UI modules)
    Affected if Plugin install functionality exists in the installation
  3. Identify user roles with plugin install access
    Review user role permissions, access control lists, or configuration files that define which user roles can execute plugin install commands
    Affected if Lower-privileged or untrusted users have permission to run plugin install commands
  4. Inspect plugin install input path configurations
    Examine plugin configuration files, environment settings, or plugin install parameter definitions for any path handling that could allow path traversal or arbitrary file access
    Affected if Plugin install accepts unvalidated file paths or contains path-related misconfigurations

You are affected if your OpenClaw version is between 2026.5.20 and 2026.6.8 inclusive AND lower-privileged users can access the plugin install functionality with misconfigured input path handling enabled.

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.9 or later
Fixed in 2026.6.9
Interim mitigation

Upgrade to OpenClaw version 2026.6.9 or later to obtain the patched version. Additionally, review and harden plugin install command authorization policies and input path validation until the upgrade can be applied.

Recommended fix Moderate confidence

2026.6.9 or later

  1. 1. Identify the currently installed OpenClaw version by checking the application version or package manager
  2. 2. Back up all OpenClaw configuration files, plugins, and data before proceeding with the upgrade
  3. 3. Upgrade OpenClaw to version 2026.6.9 or later using the appropriate package manager or installation method (e.g., pip install openclaw>=2026.6.9, apt-get upgrade openclaw, or docker pull openclaw:2026.6.9)
  4. 4. Verify the upgrade was successful by confirming the installed version matches or exceeds 2026.6.9
  5. 5. Test plugin installation functionality to ensure the privilege escalation fix is working correctly
  6. 6. Review user permissions and plugin configurations to confirm the intended authorization boundaries are enforced

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-62194 — 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-62194 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