CVE-2026-53838: OpenClaw: Node pairing reconnection could confuse approval scope state

OpenClaw pairs remote nodes to a Gateway and approves each with a scope. In affected versions, a node session that was paired or was reconnecting could mutate the pairing state, and that changed the approval scope decision. The result is that a node could hold or present more authority than the operator intended. The weakness is classed as a time-of-check to time-of-use race (CWE-367). The sources do not describe the reconnection sequence or the timing window.

The CVSS 4.0 vector is network, low complexity, low privileges, no user interaction. The low privilege requirement points to an attacker who already has a paired node or node session. They gain broader node authority, with high integrity impact. The advisory does not list what the extra authority allows, so it depends on your node setup.

The two CVSS scores in the data disagree: 4.0 gives 6.0 and 3.1 gives 9.8. The advisory text and the 4.0 vector match a medium issue that needs an existing node.

Affected: npm openclaw before 2026.5.27. Only setups that use node pairing, with the feature enabled and reachable, are exposed.

npm ls -g openclaw

Drop -g for a project install. Review the list of paired nodes in your Gateway to see which ones exist.

Update to openclaw 2026.5.27, the first stable patched version.

npm install -g [email protected]

Until you can update, the advisory advises revoking unexpected node pairings and re-pairing only trusted nodes. It also suggests narrow channel and tool allowlists, not sharing one Gateway between mutually untrusted users, and disabling node pairing if you do not need it.

The sources give no log line. List paired nodes and compare each node's current approval scope with what you approved. Look for nodes that reconnected and now hold broader scope. Review Gateway logs for repeated reconnects from the same node shortly before a scope change. Revoke any pairing you cannot account for.

Summary

Node pairing reconnection could confuse approval scope state. In affected versions, a paired or reconnecting node session could mutate pairing state in a way that changed the approval scope decision.

This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed.

Impact

When the affected feature is enabled and reachable, this could restore or present broader node authority than the operator intended. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path.

Patched Versions

The first stable patched version is 2026.5.27.

Mitigations

revoke unexpected node pairings and re-pair only trusted nodes until patched. As general hardening, keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.