dbcve.org
OpenclawApplication

CVE-2026-33575

HIGH · 7.5 CVSS v3.1 Published 2026-03-29
Fix available
A fix is available. Upgrade to 2026.3.12 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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.3.12 embeds long-lived shared gateway credentials directly in pairing setup codes generated by /pair endpoint and OpenClaw qr command. Attackers with access to leaked setup codes from chat history, logs, or screenshots can recover and reuse the shared gateway credential outside the intended one-time pairing flow.

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 embeds long-lived shared gateway credentials directly in pairing setup codes generated by the /pair endpoint and qr command. These codes are visible in chat history, logs, or screenshots, allowing attackers to recover and reuse the static credentials outside the intended one-time pairing flow.

MitigationReplace long-lived embedded credentials with ephemeral, one-time-use pairing codes, or implement credential rotation after successful pairing to prevent reuse of leaked credentials.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 OpenClaw version
    Run the version command or check the installed package version to determine if it is less than 2026.3.12
    Affected if Installed version is less than 2026.3.12
  2. Identify pairing usage
    Review logs, chat history, and system records for any /pair endpoint invocations or qr command executions
    Affected if Pairing has been performed and pairing codes were generated or transmitted
  3. Examine pairing code exposure
    Search logs, chat archives, and screenshot storage for any pairing setup codes that may contain embedded credentials
    Affected if Pairing codes are visible in logs, chat history, or were captured in screenshots
  4. Verify credential reuse
    Check if the same pairing credentials have been observed in multiple pairing sessions or outside the initial pairing flow
    Affected if Static credentials from pairing codes remain valid and reusable across sessions
  5. Review access logs
    Inspect gateway or system access logs for authentication attempts using credentials that originated from pairing codes
    Affected if Authentication attempts use credentials that match those from historical pairing codes

You are affected if OpenClaw version is less than 2026.3.12 and pairing has been performed, creating opportunity for credential exposure in logs, chat, or screenshots.

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.3.12 or later
Fixed in 2026.3.12
Interim mitigation

Replace long-lived embedded credentials with ephemeral, one-time-use pairing codes, or implement credential rotation after successful pairing to prevent reuse of leaked credentials.

Recommended fix Moderate confidence

2026.3.12

  1. 1. Check current OpenClaw version by running 'openclaw --version' or checking the installed package
  2. 2. Backup any existing OpenClaw configuration and data files
  3. 3. Upgrade OpenClaw to version 2026.3.12 or later using the package manager or build system used in your environment (e.g., pip install openclaw --upgrade, apt update && apt upgrade openclaw, or equivalent)
  4. 4. After upgrading, verify the version with 'openclaw --version' to confirm 2026.3.12 or newer is installed
  5. 5. Test the /pair endpoint and qr command to ensure pairing functionality works correctly with the updated version

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,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 $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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