CVE-2026-28391

On Windows nodes, exec requests were executed via cmd.exe /d /s /c <rawCommand>. In allowlist/approval-gated mode, the allowlist analysis did not model Windows cmd.exe parsing and metacharacter behavior. A crafted command string could cause cmd.exe to interpret additional operations (for example command chaining via &, or expansion via %...% / !...!) beyond what was allowlisted/approved.

Affected Packages / Versions

• Package: openclaw (npm)
• Affected: <= 2026.2.1
• Patched: >= 2026.2.2
• Latest (npm) as of 2026-02-14: 2026.2.13

Details

• Default installs: Not affected unless you opt into exec allowlist/approval gating on Windows nodes.
• Windows execution uses cmd.exe via src/infra/node-shell.ts.
• The fix hardens Windows allowlist enforcement by:
  • Passing the platform into allowlist analysis and rejecting Windows shell metacharacters.
  • Treating cmd.exe invocation as not allowlist-safe on Windows.
  • Avoiding cmd.exe entirely in allowlist mode by executing the parsed argv directly when possible.

Fix Commit(s)

• a7f4a53ce80c98ba1452eb90802d447fca9bf3d6

Thanks @simecek for reporting.

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2026-28391 has a CVSS score of 9.8 (High). The vector is network-reachable, no 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.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-28391? CVE-2026-28391 is a high-severity OS command injection vulnerability in openclaw (npm), affecting versions < 2026.2.2. It is fixed in 2026.2.2. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
2. How severe is CVE-2026-28391? CVE-2026-28391 has a CVSS score of 9.8 (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-28391? openclaw (npm) versions < 2026.2.2 is affected.
4. Is there a fix for CVE-2026-28391? Yes. CVE-2026-28391 is fixed in 2026.2.2. Upgrade to this version or later.
5. Is CVE-2026-28391 exploitable, and should I be worried? Whether CVE-2026-28391 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-28391 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-28391? Upgrade openclaw to 2026.2.2 or later.