Security readout for executives and security teams
Plain-English summary
OpenClaw pairing setup codes before 2026.3.12 could contain long-lived gateway credentials. If those codes appear in chat, logs, tickets, or screenshots, someone with access to them may reuse the credential after pairing should have ended.
Executive priority
Treat this as a high-priority credential exposure issue. Patch quickly, then focus on cleanup: leaked setup codes may remain useful until associated gateway credentials are rotated or invalidated.
Technical view
The issue is CWE-522 credential exposure in OpenClaw before 2026.3.12. The /pair endpoint and OpenClaw qr command embedded shared gateway credentials directly in setup codes, enabling reuse outside the intended one-time pairing flow if the code leaked.
Likely exposure
Organizations using OpenClaw versions before 2026.3.12 are the stated exposure group. Risk is highest where pairing codes were copied into logs, support systems, chat, documentation, screenshots, or other retained records.
Exploitation context
The bundle does not cite active exploitation and KEV is false. Exploitation depends on access to previously generated setup codes, so this is primarily a credential leakage and reuse risk rather than a remote scanning-only issue.
Researcher notes
The source bundle identifies the vulnerable surfaces as /pair and the OpenClaw qr command. It does not provide detailed patch mechanics, exploit telemetry, or confirmed compromise data, so validation should stay focused on version status and credential exposure paths.
Mitigation direction
- Upgrade OpenClaw to 2026.3.12 or later.
- Review vendor guidance for credential rotation requirements.
- Rotate shared gateway credentials exposed through old setup codes.
- Remove historical pairing codes from logs, chats, tickets, and screenshots.
- Restrict access to systems that may retain pairing setup codes.
Validation and detection
- Inventory OpenClaw deployments and confirm versions are 2026.3.12 or later.
- Identify where pairing setup codes may have been stored or shared.
- Check logs, support records, and chat history for retained setup codes.
- Confirm exposed credentials were rotated or invalidated.
- Review pairing workflow to ensure codes are treated as sensitive secrets.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-522: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-33575 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (4.0)
- Known Exploited
- No
- Published
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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.6HighVector: 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
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-7h7g-x2px-94hj)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: OpenClaw < 2026.3.12 - Long-lived Credential Exposure in Pairing Setup CodesCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insufficiently Protected Credentials
Insufficiently Protected Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.