Security readout for executives and security teams
Plain-English summary
OpenClaw has a high-severity authorization flaw that can let a lower-trust user perform actions meant for stronger roles. The issue is tied to the device.pair.approve feature in versions before 2026.5.27. Business risk is elevated where OpenClaw is reachable by authenticated low-privilege users.
Executive priority
Prioritize remediation for internet-facing or broadly accessible OpenClaw deployments. The vulnerability can cross authorization boundaries and affects confidentiality, integrity, and availability, but current sources do not confirm active exploitation.
Technical view
CVE-2026-62218 is a CWE-862 missing-authorization issue in OpenClaw device.pair.approve. A caller with lower trust can bypass role-management checks through configured input paths and perform higher-authorization actions. CVSS 3.1 is 8.8, network-reachable, low complexity, low privileges, no user interaction.
Likely exposure
Likely exposure is OpenClaw deployments running 2026.1.20 or other versions before 2026.5.27, especially where configured input paths allow lower-trust callers to reach device.pair.approve.
Exploitation context
The provided sources do not state active exploitation, and the CVE is not marked KEV. Exploitation requires some privileges, but no user interaction and low complexity are indicated by the CVSS vector.
Researcher notes
Evidence is limited to the CVE record and advisory metadata supplied here. No CPEs are listed. Treat the version range and remediation guidance as source-bound, and confirm exact affected builds against vendor advisory details before broad scoping.
Mitigation direction
- Upgrade OpenClaw to 2026.5.27 or later where applicable.
- Review vendor advisory for any deployment-specific mitigation guidance.
- Restrict access to device pairing flows to trusted roles only.
- Audit configured input paths that can reach device.pair.approve.
- Monitor for unexpected device-pair approvals or role-management activity.
Validation and detection
- Inventory OpenClaw versions across all environments.
- Confirm affected systems are below 2026.5.27.
- Review route and input-path configuration for device.pair.approve exposure.
- Check logs for unexpected approval events by low-trust accounts.
- Validate upgraded systems enforce role-management checks in staging.
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-862: 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-62218 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.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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-8v95-qqcm-qp9h)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: OpenClaw 2026.1.20 < 2026.5.27 Authorization Bypass via device.pair.approveCVE 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.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.