Security readout for executives and security teams
Plain-English summary
OpenClaw can mistakenly carry a direct-message sender approval from one account into another account. In a multi-account deployment, this could let a previously approved sender bypass the approval boundary for a different account. The known impact is limited confidentiality and integrity exposure, not service disruption.
Executive priority
Schedule remediation during the next normal maintenance window unless OpenClaw is business-critical or heavily multi-account. Prioritize faster if DM pairing controls protect sensitive communications or regulated data.
Technical view
CVE-2026-32067 is a CWE-863 authorization bypass in OpenClaw before 2026.2.26. The pairing-store access control for DM pairing policy can reuse approvals across accounts, allowing automatic acceptance in another account without explicit approval. CVSS is 3.7 with network access, low privileges, user interaction, high complexity, and no availability impact.
Likely exposure
Exposure is mainly organizations running OpenClaw before 2026.2.26 in multi-account deployments using direct-message pairing approvals. Single-account deployments or instances not using DM pairing appear less exposed based on the source bundle, but evidence is incomplete.
Exploitation context
No KEV listing or cited source in the bundle states active exploitation. Exploitation requires network access, low privileges, user interaction, and high complexity. The scenario depends on an attacker already being approved as a sender in one account, then benefiting from approval reuse in another.
Researcher notes
The bundle identifies the flaw class, affected version boundary, CVSS vector, and patch references, but does not include detailed code behavior or exploitation evidence. Avoid assuming broader account takeover or data access beyond limited confidentiality and integrity impact.
Mitigation direction
- Upgrade OpenClaw to 2026.2.26 or later where applicable.
- Review the GitHub advisory and patch commits for deployment-specific guidance.
- Inventory multi-account deployments using direct-message pairing approvals.
- Review existing DM pairing approvals for unintended cross-account acceptance.
- If upgrade is delayed, restrict risky multi-account DM pairing workflows.
Validation and detection
- Confirm all OpenClaw instances are version 2026.2.26 or later.
- Identify whether any deployment uses multi-account DM pairing policy.
- Verify sender approval decisions are scoped to the intended account.
- Review pairing-store records for reused approvals across accounts.
- Audit logs for unexpected DM pairing acceptances between accounts.
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-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior 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-32067 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
- Low
- CVSS
- 3.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A: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:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N1.22.5VulnCheckCVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
2LowVector: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
3.7LowVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/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-vjp8-wprm-2jw9)CVE reference, VulnCheck · vendor-advisory
- Patch Commit #1CVE reference, VulnCheck · patch
- Patch Commit #2CVE reference, VulnCheck · patch
- VulnCheck Advisory: OpenClaw < 2026.2.26 - Cross-Account Authorization Bypass in DM Pairing StoreCVE 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.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.