dbcve.org
OpenclawApplication

CVE-2026-62193

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-13
Fix available
A fix is available. Upgrade to 2026.6.9 or later.
See remediation →
71/100
Remediation priority · Elevated
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.6.5 before 2026.6.9 contain a vulnerability in the plugin install wrappers that could skip the install policy (authorization) check. When the affected feature is enabled and reachable, a lower-trust caller or a configured input path could execute or persist actions beyond the caller's intended authorization. Impact depends on the operator's configuration and whether lower-trust input can reach the affected path. The issue is fixed in 2026.6.9.

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 plugin install wrappers have an authorization bypass vulnerability where the install policy check is conditionally skipped. When the affected feature is enabled and reachable, lower-privilege callers or untrusted input paths can execute or persist plugin installations beyond their intended authorization level, leading to privilege escalation.

MitigationUpgrade OpenClaw to version 2026.6.9 or later. Review configuration to identify and restrict any lower-trust input paths that may reach the affected plugin install wrappers.

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.5, < 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Identify installed OpenClaw version
    Run the command to display the OpenClaw version (e.g., openclaw --version, or check the product's About/Version dialog in the GUI)
    Affected if The displayed version is 2026.6.5, 2026.6.6, 2026.6.7, or 2026.6.8 (falls within >= 2026.6.5 and < 2026.6.9)
  2. Locate plugin install configuration
    Search for configuration files related to plugin installation in the OpenClaw installation directory or user data folder - look for files named plugin.conf, plugins.cfg, or similar
    Affected if A plugin installation configuration file exists and the feature is enabled (e.g., a setting like enable_plugin_install or allow_remote_plugins is set to true)
  3. Verify plugin wrapper accessibility
    Examine the OpenClaw API or wrapper configuration to determine if the plugin install endpoints are exposed to lower-privilege callers or unauthenticated input paths
    Affected if The plugin install wrappers are reachable from untrusted input paths or accessible to users without sufficient authorization
  4. Inspect authorization policy for plugin installs
    Review the authorization policy or access control configuration for plugin installation operations - check for any conditional logic that may skip policy checks
    Affected if The policy check for plugin installations can be bypassed or conditionally skipped based on certain input conditions or feature flags

You are affected if your OpenClaw version is 2026.6.5 through 2026.6.8 AND the plugin install feature is enabled with accessible input paths that can bypass the authorization check.

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 OpenClaw to version 2026.6.9 or later. Review configuration to identify and restrict any lower-trust input paths that may reach the affected plugin install wrappers.

Recommended fix High confidence

2026.6.9

  1. 1. Back up the current OpenClaw installation and configuration
  2. 2. Download OpenClaw version 2026.6.9 from the official repository
  3. 3. Verify the integrity and authenticity of the downloaded package
  4. 4. Stop the OpenClaw service
  5. 5. Install or apply the upgrade to version 2026.6.9
  6. 6. Verify the installation completed successfully
  7. 7. Start the OpenClaw service
  8. 8. Verify the plugin install authorization checks are now enforced as expected

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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