CVE-2026-32010

This issue applies to a non-default configuration only.
If sort is manually added to tools.exec.safeBins, OpenClaw could treat sort --compress-program=<prog> as valid safe-bin usage.
In security=allowlist + ask=on-miss, this could satisfy allowlist checks and skip operator approval, while GNU sort may invoke an external program via --compress-program.

Affected Packages / Versions

• Ecosystem: npm
• Package: openclaw
• Affected: <= 2026.2.21-2
• Patched (planned next release): >= 2026.2.22

Default Installations

Default installs are not impacted by this specific path because sort is not included in default tools.exec.safeBins.

Technical Details

• sort safe-bin profile allowed --compress-program as a value flag.
• Safe-bin satisfaction could therefore mark allowlist checks as satisfied.
• In ask=on-miss, satisfied allowlist checks skip approval prompts.

Fix Commit(s)

• 57fbbaebca4d34d17549accf6092ae26eb7b605c

OpenClaw thanks @tdjackey for reporting.

• Type: approval/allowlist bypass in optional safe-bin configuration
• Scope: deployments that explicitly include sort in tools.exec.safeBins and use allowlist + ask=on-miss
• Consequence: an external program may run under the OpenClaw process context without expected approval

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-32010 has a CVSS score of 8.8 (Medium). The vector is network-reachable, low 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.22); upgrading removes the vulnerable code path.

Kodem intelligence

• Block --compress-program in safe-bin sort policy.
• Add unit and e2e regression coverage for sort --compress-program denial in safe-bin mode.

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