CVE-2026-26325: OpenClaw Node host system.run rawCommand/command mismatch can bypass allowlist/approvals
In OpenClaw's node host, the `system.run` handler checked the allowlist and approval policy against `rawCommand` but executed a different `command[]` argv. A caller who can invoke `system.run` can run commands outside the allowlist without an approval prompt. The `openclaw` npm package below 2026.2.14 is affected when a node uses `security=allowlist`. Upgrade to 2026.2.14.
Published Feb 17, 2026 · Updated Feb 20, 2026 · Analysis Nov 1, 2026
What an attacker can do
system.run takes two descriptions of the same command: a rawCommand string and a command[] argv array. Policy evaluation used the first. Execution used the second. Nothing enforced that they matched.
An attacker supplies an allowlisted rawCommand, such as a harmless listed binary, and a command[] that runs something else. The policy sees the listed command, and neither the allowlist nor the ask=on-miss approval prompt fires.
The advisory narrows the exposure. It applies only to the node host or companion node execution path, with security=allowlist and approvals driven by allowlist misses, for example ask=on-miss, and only if an attacker can invoke system.run. Default and non-node setups are not affected. The CVSS 3.1 vector requires high privileges (PR:H), which fits: the caller already has access to the invocation path. On a node, the result is arbitrary command execution on that machine, defeating the control the operator set to limit it.
Who is affected
The npm package openclaw at 2026.2.13 and earlier. Only deployments that run a node host with allowlist execution policy and prompting on allowlist misses are exposed. Check the version on the gateway and on each node.
npm ls -g openclaw
openclaw --versionThen check the exec policy config for security=allowlist and ask=on-miss.
openclaw
- Ecosystem
- npm
- Affected
- < 2026.2.14
- Fixed in
- 2026.2.14
- Check
npm ls openclaw
How to fix it
Upgrade the gateway and every node host to 2026.2.14.
npm install -g [email protected]Commit cb3290fc adds validateSystemRunCommandConsistency() in src/infra/system-run-command.ts. It compares rawCommand with the argv, or with the inner command of a shell wrapper such as sh -lc or cmd.exe /c. The gateway runs it in sanitizeSystemRunParamsForForwarding() and the node runs it in handleInvoke(). A mismatch returns INVALID_REQUEST: rawCommand does not match command. No workaround is named, so update nodes as well as the gateway.
How to tell if you were hit
Search gateway and node logs for INVALID_REQUEST errors with code RAW_COMMAND_MISMATCH or MISSING_COMMAND. Those show blocked attempts after the upgrade. On unpatched nodes, compare logged system.run requests against the processes that ran: a rawCommand that differs from the executed argv is the signature. Check shell history and process accounting on node hosts for commands that never appeared in the allowlist or the approval log.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
A mismatch between rawCommand and command[] in the node host system.run handler could cause allowlist/approval evaluation to be performed on one command while executing a different argv.
Affected Configurations
This only impacts deployments that:
- Use the node host / companion node execution path (
system.runon a node). - Enable allowlist-based exec policy (
security=allowlist) with approval prompting driven by allowlist misses (for exampleask=on-miss). - Allow an attacker to invoke
system.run.
Default/non-node configurations are not affected.
Impact
In affected configurations, an attacker who can invoke system.run can bypass allowlist enforcement and approval prompts by supplying an allowlisted rawCommand while providing a different command[] argv for execution.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
<= 2026.2.13 - Patched version:
>= 2026.2.14(planned next release)
Fix
Enforce rawCommand/command[] consistency (gateway fail-fast + node host validation).
Fix Commit(s)
- cb3290fca32593956638f161d9776266b90ab891
Release Process Note
This advisory pre-sets the patched version to the planned next release (2026.2.14). Once [email protected] is published to npm, the advisory can be published without further edits.
Thanks @christos-eth for reporting.
Credited to christos-eth.
Questions
- Are default OpenClaw installs affected by CVE-2026-26325?
No. The advisory says default and non-node configurations are not affected. The flaw needs the node host path,
security=allowlist, and a caller who can invokesystem.run.- What does the attacker send?
An allowlisted
rawCommandtogether with a differentcommand[]argv. The policy evaluated the first and the node executed the second.- Is there a fix version?
Yes, 2026.2.14. The fix requires rawCommand and command[] to agree, at both the gateway and the node host.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-62197
OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs
medium8.5Oct 21, 2026CVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026
