CVE-2026-22217

shell-env fallback trusted prefix-based executable paths for $SHELL, allowing execution of attacker-controlled binaries in local/runtime-env influence scenarios.

Details

In affected versions, shell selection accepted either:

1. a shell listed in /etc/shells, or
2. any executable under hardcoded trusted prefixes (/bin, /usr/bin, /usr/local/bin, /opt/homebrew/bin, /run/current-system/sw/bin).

The selected shell was then executed as a login shell (-l -c 'env -0') for PATH/environment probing.

On systems where a trusted-prefix directory is writable (for example common Homebrew layouts under /opt/homebrew/bin) and runtime $SHELL can be influenced, this enabled attacker-controlled binary execution in OpenClaw process context.

The fix removes the trusted-prefix executable fallback and now trusts only shells explicitly registered in /etc/shells; otherwise it falls back to /bin/sh.

Affected Packages / Versions

• Package: openclaw (npm)
• Affected versions: >= 2026.2.22, <= 2026.2.22-2
• Latest published vulnerable version: 2026.2.22-2
• Patched versions (released): >= 2026.2.23

Fix Commit(s)

• ff10fe8b91670044a6bb0cd85deb736a0ec8fb55

Release Process Note

This advisory sets patched_versions to the released version (2026.2.23).
This advisory now reflects released fix version 2026.2.23.

OpenClaw thanks @tdjackey for reporting.

CVE-2026-22217 has a CVSS score of 6.1 (Medium). The vector is requires local access, 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.23); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-22217? CVE-2026-22217 is a medium-severity security vulnerability in openclaw (npm), affecting versions >= 2026.2.22, < 2026.2.23. It is fixed in 2026.2.23.
2. How severe is CVE-2026-22217? CVE-2026-22217 has a CVSS score of 6.1 (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-22217? openclaw (npm) versions >= 2026.2.22, < 2026.2.23 is affected.
4. Is there a fix for CVE-2026-22217? Yes. CVE-2026-22217 is fixed in 2026.2.23. Upgrade to this version or later.
5. Is CVE-2026-22217 exploitable, and should I be worried? Whether CVE-2026-22217 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-22217 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-22217? Upgrade openclaw to 2026.2.23 or later.