An OpenClaw version before 2026.3.22 contains a privilege‑escalation flaw in the device.pair.approve feature. The code fails to validate that the operator.approver's scopes cover the requested device pairing, allowing an approver to grant pairings with scopes higher than the operator actually holds. This scope bypass can elevate an operator’s rights to operator.admin, giving the attacker the ability to execute arbitrary code on the underlying Node infrastructure. The weakness corresponds to CWE‑648, improper authorization.

OpenClaw instances running any release earlier than 2026.3.22 are affected. The vulnerability impacts the OpenClaw application itself, which is deployed on Node.js environments, and relies on the device.pair.approve API. Users of the OpenClaw product should verify the deployment version and ensure it is updated to 2026.3.22 or later.

The CVSS score of 8.7 indicates a high severity, and although the EPSS score is unavailable, the vulnerability is known to be exploitable via the device.pair.approve endpoint. Since it is not listed in CISA’s KEV catalog, there is no confirmed field‑of‑view data yet, but the lack of proper scope validation suggests that an attacker who can trigger the approve action—such as through an authenticated session or API call—can gain elevated privileges. This makes the vulnerability relatively easy to exploit in any environment where an operator with pairing approval rights also has network access to the API.