openclaw
Affected
- introduced
0, fixed2026.2.14(semver)
Fixed versions
2026.2.14
Fix
- Fixed version
2026.2.14npm install [email protected]
Advisory
Also known as: CVE-2026-28466
OpenClaw Vulnerable to Remote Code Execution via Node Invoke Approval Bypass in Gateway
Summary
A remote code execution (RCE) vulnerability in the gateway-to-node invocation path allowed an authenticated gateway client to bypass node-host exec approvals by injecting internal control fields into node.invoke parameters.
Affected Component
node.invoke for node command system.runsystem.runImpact
If an attacker can authenticate to a gateway (for example via a leaked/shared gateway token or a paired device token with operator.write), they could execute arbitrary commands on connected node hosts that support system.run. This can lead to full compromise of developer workstations, CI runners, and servers running the node host.
Technical Details
The gateway forwarded user-controlled params to node hosts without sanitizing internal approval fields. The node host treated params.approved === true and/or params.approvalDecision as sufficient to skip the approval workflow.
Fix
Patched in OpenClaw `2026.2.14`.
318379cdb8d045da0009b0051bd0e712e5c65e2da7af646fdab124a7536998db6bd6ad567d2b06b0c1594627421f95b6bc4ad7c606657dc75b5ad0ce0af76f5f0e93540efbdf054895216c398692afcdsystem.run user input.params.runId references a valid exec.approval.request record and the request context matches. Approval IDs are bound to the requesting device identity (stable across reconnects), preventing replay by other clients.system.run parameters, preventing future control-field smuggling.Mitigations
2026.2.14 or later.system.run at the gateway (gateway.nodes.denyCommands) and/or by configuring node exec security to deny.Credits
OpenClaw thanks @222n5 for reporting this issue.
Critical Basis: The source's own band: CRITICAL
0, fixed 2026.2.14 (semver)2026.2.14
2026.2.14npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0