CVE-2026-62223: Openclaw Auth Bypass Vulnerability

CVE-2026-62223 Overview

CVE-2026-62223 is an authorization bypass vulnerability in OpenClaw versions before 2026.5.18. The flaw resides in the device-pair approval feature and allows lower-trust callers to execute actions beyond their intended authorization scope. Attackers with limited privileges can leverage misconfigured input paths to execute or persist unauthorized actions when the affected feature is enabled and reachable over the network. The vulnerability is tracked under CWE-863: Incorrect Authorization and affects the OpenClaw Node.js package distribution.

Critical Impact
Authenticated attackers with low privileges can bypass authorization checks in the device-pair approval flow to gain high impact on confidentiality, integrity, and availability of the affected OpenClaw deployment.

Affected Products

OpenClaw versions prior to 2026.5.18
OpenClaw Node.js package distribution
Deployments with the device-pair approval feature enabled and network-reachable

Discovery Timeline

2026-07-17 - CVE-2026-62223 published to NVD
2026-07-20 - Last updated in NVD database

Technical Details for CVE-2026-62223

Vulnerability Analysis

The vulnerability stems from an incorrect authorization check within the OpenClaw device-pair approval workflow. The feature is designed to validate that a caller holds the required trust level before approving device pairings or executing related administrative actions. Instead, the implementation accepts input paths that route lower-trust callers into privileged code branches. This bypass permits actions that should be gated behind stricter role checks.

Because the flaw is reachable over the network with only low privileges required and no user interaction, an authenticated attacker holding a basic account can weaponize the device-pair endpoint. Successful exploitation yields high impact on confidentiality, integrity, and availability of the affected instance.

Root Cause

The root cause is an incorrect authorization pattern [CWE-863] in the device-pair approval code path. Trust decisions rely on caller-supplied inputs that are not fully validated against the authenticated principal's actual role. This mismatch allows privilege boundaries to be crossed without triggering an access-control failure.

Attack Vector

The attack vector is network-based. An attacker authenticates with any valid low-privilege account, then sends crafted requests to the device-pair approval interface. By manipulating the input path parameters used in the authorization decision, the attacker triggers actions reserved for higher-trust roles. Refer to the VulnCheck Advisory on Bypass and the GitHub Security Advisory for technical specifics.

No verified public proof-of-concept code is available. See the linked advisories for details on the vulnerable flow.

Detection Methods for CVE-2026-62223

Indicators of Compromise

Unexpected successful device-pair approval events initiated by accounts that lack administrative roles
Approval or persistence actions logged from user sessions that historically only performed read operations
Repeated requests to the device-pair endpoint with unusual parameter permutations preceding a role-restricted action

Detection Strategies

Compare the authenticated principal's role in each device-pair approval log entry against the action performed, and alert on mismatches
Baseline normal device-pair traffic volume and account attribution, then flag deviations such as low-privilege accounts issuing approval calls
Correlate authentication logs with device-pair API access logs to surface sessions that escalate action scope within a short window

Monitoring Recommendations

Enable verbose audit logging on the OpenClaw device-pair approval endpoint, including caller identity, role, and input path values
Forward OpenClaw application logs to a central SIEM or data lake for retention and cross-source correlation
Monitor outbound and lateral activity from hosts running OpenClaw for signs of post-exploitation persistence

How to Mitigate CVE-2026-62223

Immediate Actions Required

Upgrade OpenClaw to version 2026.5.18 or later on all affected hosts
Inventory OpenClaw deployments and confirm whether the device-pair approval feature is enabled and network-reachable
Rotate credentials and API tokens for any accounts that could have interacted with the vulnerable endpoint
Review historical logs of the device-pair approval endpoint for unauthorized actions taken by low-privilege accounts

Patch Information

OpenClaw addressed the authorization bypass in version 2026.5.18. Administrators should update the Node.js package to the fixed release. Consult the GitHub Security Advisory GHSA-hx85-fgcw-9vrc for release notes and upgrade guidance.

Workarounds

Disable the device-pair approval feature until the patched version can be deployed
Restrict network access to the OpenClaw management interface using firewall rules or reverse-proxy allowlists
Enforce least-privilege role assignments and remove unused low-privilege accounts that could serve as an initial foothold
Add an upstream authorization layer, such as an API gateway, that validates caller roles against the requested action

bash

# Upgrade OpenClaw to the fixed release via npm
npm install openclaw@2026.5.18

# Verify the installed version
npm ls openclaw