UTC
Critical

OpenClaw Vulnerable to Remote Code Execution via Node Invoke Approval Bypass in Gateway

CVE-2026-28466 · GHSA-gv46-4xfq-jv58 · published 2026-03-02 · updated 2026-03-06

Severity
Critical
CVSS score
9.9
Chance of exploitation (EPSS)
0.47%
Fixed in
2026.2.14
  • Exploitation No known exploitation
  • Automatable No
  • Technical impact Partial
  • CISA SSVC
What it is

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.

What to do

Upgrade openclaw to 2026.2.14 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Patched in OpenClaw 2026.2.14. Commits: 318379cdb8d045da0009b0051bd0e712e5c65e2d a7af646fdab124a7536998db6bd6ad567d2b06b0 c1594627421f95b6bc4ad7c606657dc75b5ad0ce 0af76f5f0e93540efbdf054895216c398692afcd Gateway strips untrusted approval control fields from system.run user input. Gateway only re-attaches approval flags when 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. Gateway forwards only an allowlisted set of system.run parameters, preventing future control-field smuggling.

If you cannot upgrade yet

Upgrade to 2026.2.14 or later. Restrict access to the gateway (do not expose it to untrusted networks/users). Rotate gateway credentials if you suspect token/password exposure. Disable remote command execution on nodes by blocking system.run at the gateway (gateway.nodes.denyCommands) and/or by configuring node exec security to deny.

Affected
PackageRegistryAffectedFixed in
openclawnpm< 2026.2.142026.2.14

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].