dbcve.org
OpenclawApplication

CVE-2026-32905

HIGH · 8.3 CVSS v3.1 Published 2026-05-29
Fix available
A fix is available. Upgrade to 2026.5.4 or later.
See remediation →
89/100
Remediation priority · High
Remotely reachable Zero-click

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.5.4 contains an authorization bypass vulnerability in the bundled device-pair plugin that allows non-owner authorized chat senders to issue device-pairing bootstrap codes without proper scope validation. Attackers with chat command access can create setup codes to enroll devices with operator/node capabilities, granting persistent credentials until manual removal.

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 before 6.5.4 contains an authorization bypass in its bundled device-pair plugin where scope validation is missing on device-pairing bootstrap code generation. Attackers with any authorized chat command access can create setup codes that enroll devices with operator/node capabilities, granting persistent elevated credentials.

MitigationUpgrade to OpenClaw 6.5.4 or later to obtain the patched version with proper scope validation. Additionally, audit existing device pairings and revoke any unauthorized operator/node credentials, and consider restricting chat command access until the patch is 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.4

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. Verify OpenClaw version
    Locate and read the installed OpenClaw version identifier (typically via --version flag, about dialog, or version file in the installation directory)
    Affected if The installed version is any release prior to 2026.5.4
  2. Confirm device-pair plugin is present
    Inspect the OpenClaw installation for the bundled device-pair plugin module or component (check plugins directory, bundled modules, or component listing)
    Affected if The device-pair plugin exists in the installation and is available for use
  3. Check for operator or node capability enrollments
    Review device enrollment records or logs that show devices registered with elevated operator or node capabilities via the pairing system
    Affected if Any device enrollments with operator or node capabilities exist that were created through the device-pair bootstrap process and were not initiated by the account owner
  4. Audit recent device-pair bootstrap activity
    Examine authentication or pairing logs for bootstrap code generation events, looking for entries where non-owner accounts generated setup codes
    Affected if Bootstrap codes were generated or processed by accounts other than the device owner

You are affected if OpenClaw version is below 2026.5.4 AND the bundled device-pair plugin is present AND any operator/node capability devices were enrolled via non-owner initiated bootstrap codes.

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.5.4 or later
Fixed in 2026.5.4
Interim mitigation

Upgrade to OpenClaw 6.5.4 or later to obtain the patched version with proper scope validation. Additionally, audit existing device pairings and revoke any unauthorized operator/node credentials, and consider restricting chat command access until the patch is applied.

Recommended fix High confidence

OpenClaw 2026.5.4

  1. 1. Identify all deployed instances of OpenClaw versions prior to 2026.5.4
  2. 2. Review current backup strategy and ensure recent backups are available before upgrading
  3. 3. Upgrade OpenClaw to version 2026.5.4 or later
  4. 4. After upgrade, audit the device-pair plugin configuration to verify authorization controls are enforced
  5. 5. Review system logs for any suspicious device-pairing bootstrap code generation that occurred prior to the upgrade
  6. 6. Revoke any unauthorized device credentials that may have been enrolled during the exploitation window

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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