Which versions of Openclaw are affected by CVE-2026-33575?

CVE-2026-33575 affects OpenClaw gateway pairing mechanism, allowing attackers to extract long-lived credentials from pairing setup codes visible in chat logs, screenshots, or system logs.. A patch is available.

How to fix or mitigate CVE-2026-33575?

Within 24 hours: Audit and restrict access to chat logs, screenshots, and system logs containing OpenClaw pairing codes; notify users to avoid sharing QR codes or pairing tokens in unencrypted communications. Within 7 days: Upgrade all OpenClaw deployments to version 2026.3.12 or later. Within 30 days: Conduct post-upgrade validation of gateway access controls; review access logs for any unauthorized gateway authentication attempts; implement controls to prevent pairing code exfiltration (e.g., log sanitization, restricted screenshot capabilities).

Openclaw CVE-2026-33575

Q: What is the CVSS score of CVE-2026-33575?

CVE-2026-33575 has a CVSS 4.0 base score of 8.6 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-17029 HIGH

Insufficiently Protected Credentials (CWE-522)

2026-03-29 VulnCheck

Information Disclosure Openclaw

8.6

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

8.6 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Scope

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 06:11 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

2026.3.12

EUVD ID Assigned

Mar 29, 2026 - 13:15 euvd

EUVD-2026-17029

Analysis Generated

Mar 29, 2026 - 13:15 vuln.today

CVE Published

Mar 29, 2026 - 12:44 nvd

HIGH 8.6

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

1 npm packages depend on openclaw (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.3.12.

DescriptionCVE.org

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.

AnalysisAI

Credential exposure in OpenClaw gateway pairing mechanism allows remote attackers to extract and reuse long-lived shared gateway credentials embedded in pairing setup codes. Attackers who obtain QR codes or pairing tokens from chat logs, screenshots, or system logs can recover persistent gateway credentials intended for one-time use, enabling unauthorized gateway access without authentication. EPSS data not available; no public exploit identified at time of analysis. Affects OpenClaw versions prior to 2026.3.12.

Technical ContextAI

OpenClaw's gateway pairing implementation (specifically the /pair endpoint and qr command functionality) violates secure credential design by embedding persistent shared secrets directly into pairing setup codes. The vulnerability stems from CWE-522 (Insufficiently Protected Credentials), where sensitive authentication material that should remain server-side is instead transmitted in client-accessible pairing tokens. Proper pairing flows should use ephemeral session tokens or challenge-response protocols that never expose long-lived credentials in user-visible artifacts. The affected component is OpenClaw (cpe:2.3:a:openclaw:openclaw), a gateway or device management platform. The design flaw means any capture of the pairing code-through screenshot sharing, log file exposure, or chat history retention-permanently compromises the gateway credential rather than just a single pairing session.

RemediationAI

Upgrade to OpenClaw version 2026.3.12 or later, which addresses the credential embedding vulnerability in pairing code generation. The patched version implements proper separation between ephemeral pairing tokens and persistent gateway credentials. Organizations should rotate all gateway credentials that may have been exposed through historical pairing codes, particularly if setup codes were shared via chat, email, ticketing systems, or stored in logs. Review access logs for unauthorized gateway connections that may indicate compromised credentials from leaked pairing codes. Consult the official security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-7h7g-x2px-94hj for migration guidance and credential rotation procedures. Additional technical details are available in the VulnCheck advisory at https://www.vulncheck.com/advisories/openclaw-long-lived-credential-exposure-in-pairing-setup-codes for threat intelligence context.