Skip to main content

OpenClaw CVE-2026-62218

| EUVDEUVD-2026-45106 HIGH
Missing Authorization (CWE-862)
2026-07-17 VulnCheck GHSA-4cxx-m26f-jmx8
8.7
CVSS 4.0 · Vendor: VulnCheck
Share

Severity by source

Vendor (VulnCheck) PRIMARY
8.7 HIGH
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/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
vuln.today AI
8.8 HIGH

Network-reachable, low-complexity authorization bypass needing an authenticated low-trust account (PR:L) and no user interaction, with high confidentiality, integrity, and availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
X

Lifecycle Timeline

3
Patch available
Jul 17, 2026 - 02:32 EUVD
Analysis Generated
Jul 17, 2026 - 00:57 vuln.today
CVE Published
Jul 17, 2026 - 00:06 cve.org
HIGH 8.7

DescriptionCVE.org

OpenClaw 2026.1.20 before 2026.5.27 contain an authorization bypass vulnerability in the device.pair.approve feature that allows lower-trust callers to bypass role-management checks. Attackers can perform actions requiring stronger authorization by reaching the affected feature through configured input paths.

AnalysisAI

Authorization bypass in OpenClaw versions 2026.1.20 through 2026.5.26 allows low-trust, authenticated callers to invoke the device.pair.approve feature and perform device-pairing approvals that should require stronger role-management authorization. Because the feature can be reached through configured input paths, an attacker holding only limited privileges can escalate their effective authority over device pairing, with high impact to confidentiality, integrity, and availability. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV, but the flaw was reported by VulnCheck and carries a CVSS 4.0 base score of 8.7.

Technical ContextAI

OpenClaw exposes a device pairing/approval workflow via a device.pair.approve action that is expected to enforce role-management (authorization) checks before granting approval. The root cause is CWE-862 (Missing Authorization): the code path that services device.pair.approve fails to consistently verify that the caller holds the required trust level, so authorization is either omitted or applied only at a layer that lower-trust callers can bypass by reaching the feature through configured input paths. The single CPE, cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*, indicates the affected component is the OpenClaw application itself rather than a bundled third-party library, so the fix is an application-level authorization enforcement change delivered in 2026.5.27.

RemediationAI

Upgrade to the fixed release: Vendor-released patch: OpenClaw 2026.5.27, which restores the role-management authorization checks on the device.pair.approve feature; consult the GitHub Security Advisory GHSA-8v95-qqcm-qp9h (https://github.com/openclaw/openclaw/security/advisories/GHSA-8v95-qqcm-qp9h) for exact upgrade guidance. If immediate patching is not possible, reduce exposure by restricting who can reach the device.pair.approve feature and the configured input paths that expose it - for example, limit device-pairing approval endpoints to trusted administrative networks or accounts and tighten the role assignments granted to lower-trust callers so fewer principals can invoke the action, accepting that this may block legitimate self-service pairing workflows. Monitor pairing-approval activity for approvals initiated by accounts that should not hold that authority until the upgrade is applied, and review the VulnCheck advisory (https://www.vulncheck.com/advisories/openclaw-authorization-bypass-via-device-pair-approve) for any additional mitigations.

CVE-2026-28446 CRITICAL POC
9.4 Mar 05

Auth bypass in OpenClaw voice-call extension before 2026.2.1. EPSS 0.68%. PoC and patch available.

CVE-2026-33579 CRITICAL POC
9.4 Mar 31

Privilege escalation in OpenClaw (pre-2026.3.28) allows unauthenticated remote attackers to gain administrative access b

CVE-2026-32042 HIGH POC
8.8 Mar 21

OpenClaw versions 2026.2.22 through 2026.2.24 contain a privilege escalation vulnerability that allows authenticated att

CVE-2026-32051 HIGH POC
8.8 Mar 21

An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.

CVE-2026-25253 HIGH POC
8.8 Feb 01

OpenClaw versions prior to 2026.1.29 automatically establish WebSocket connections to attacker-controlled gateway URLs e

CVE-2026-32846 HIGH POC
8.7 Mar 26

Path traversal in OpenClaw through version 2026.3.23 enables unauthenticated remote attackers to read arbitrary files in

CVE-2026-32064 HIGH POC
7.7 Mar 21

OpenClaw sandbox browser functionality launches x11vnc for noVNC observer sessions without requiring authentication, all

CVE-2026-32055 HIGH POC
7.6 Mar 21

OpenClaw versions before 2026.2.26 allow authenticated attackers to write arbitrary files outside the workspace director

CVE-2026-32056 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.2.22 contain a shell environment variable injection vulnerability in the system.run func

CVE-2026-32049 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consiste

CVE-2026-32048 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.3.1 contain a sandbox escape vulnerability that allows authenticated attackers with low

CVE-2026-25474 HIGH POC
7.5 Feb 19

OpenClaw versions 2026.1.30 and below fail to validate Telegram webhook secret tokens when `channels.telegram.webhookSec

Share

CVE-2026-62218 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy