CVE-2026-26325

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.run on a node).
• Enable allowlist-based exec policy (security=allowlist) with approval prompting driven by allowlist misses (for example ask=on-miss).
• Allow an attacker to invoke system.run.

Default/non-node configurations are not affected.

Affected Packages / Versions

• Package: openclaw (npm)
• Affected versions: <= 2026.2.13
• Patched version: >= 2026.2.14 (planned next release)

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.

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.

CVE-2026-26325 has a CVSS score of 7.2 (High). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.14); upgrading removes the vulnerable code path.

Kodem intelligence

Enforce rawCommand/command[] consistency (gateway fail-fast + node host validation).

1. What is CVE-2026-26325? CVE-2026-26325 is a high-severity security vulnerability in openclaw (npm), affecting versions < 2026.2.14. It is fixed in 2026.2.14.
2. How severe is CVE-2026-26325? CVE-2026-26325 has a CVSS score of 7.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-26325? openclaw (npm) versions < 2026.2.14 is affected.
4. Is there a fix for CVE-2026-26325? Yes. CVE-2026-26325 is fixed in 2026.2.14. Upgrade to this version or later.
5. Is CVE-2026-26325 exploitable, and should I be worried? Whether CVE-2026-26325 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-26325 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-26325? Upgrade openclaw to 2026.2.14 or later.