CVE-2026-42426

8.8

OpenClaw · OpenClaw

OpenClaw versions before 2026.4.8 contain an authorization flaw in the node.pair.approve method that allows users with restricted permissions to approve node pairing.

Executive summary

An improper authorization vulnerability in OpenClaw allows authenticated users with operator.write permissions to bypass pairing restrictions, potentially leading to unauthorized access to critical nodes.

Vulnerability

The vulnerability exists in the node.pair.approve method, which incorrectly accepts the operator.write scope instead of the required operator.pairing scope. This flaw allows an authenticated attacker possessing write-level privileges to perform unauthorized node pairing actions.

Business impact

Successful exploitation allows an attacker to bypass security controls and gain unauthorized access to exec-capable nodes within the infrastructure. Given the CVSS score of 8.8, this represents a high-severity risk that could lead to full system compromise or unauthorized command execution. Such access poses significant threats to data integrity and overall system availability.

Remediation

Immediate Action: Update the OpenClaw package to version 2026.4.8 or later immediately to resolve the authorization scope check.

Proactive Monitoring: Review audit logs for unexpected node pairing events or suspicious use of the node.pair.approve method by accounts with operator.write permissions.

Compensating Controls: Implement strict role-based access control (RBAC) to limit the number of users assigned the operator.write scope until the patch can be deployed.

Exploitation status

Public Exploit Available: No

Analyst recommendation

This vulnerability presents a significant risk to environment security by allowing unauthorized node pairing. Administrators must prioritize updating to version 2026.4.8 to enforce the correct authorization scopes and prevent potential privilege escalation. Failure to patch may permit attackers to gain control over sensitive infrastructure components.

More OpenClaw CVEs

Sources

Originally found and disclosed by Nicky (@nicky-cc), per the CVE Program record.