Summary
OpenClaw's tools.exec.safeBins generic fallback allowed interpreter-style inline payload execution in allowlist mode
When tools.exec.safeBins contained a binary without an explicit safe-bin profile, OpenClaw used a permissive generic fallback profile. In allowlist mode, that could let interpreter-style binaries (for example python3, node, ruby) execute inline payloads via flags like -c.
This requires explicit operator configuration to add such binaries to safeBins, so impact is limited to non-default/misconfigured deployments.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
<= 2026.2.21-2 - Patched in code:
>= 2026.2.22(planned next npm release)
Fix Commit(s)
47c3f742b6c488be26dd7b9636dbbb8676089154
Release Process Note
patched_versions is pre-set to the planned next release (>= 2026.2.22) so once that npm release is published, the advisory can be published directly without further metadata edits.
OpenClaw thanks @tdjackey for reporting.
Impact
Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
- Remove generic safe-bin fallback during allowlist evaluation.
- Require explicit safe-bin profiles for
safeBinsentries. - Add configurable
tools.exec.safeBinProfiles(global + per-agent) for safe custom binaries. - Update docs to clearly separate
safeBinsfrom command allowlist semantics.
Frequently Asked Questions
- What is GHSA-8MF7-VV8W-HJR2? GHSA-8MF7-VV8W-HJR2 is a low-severity OS command injection vulnerability in openclaw (npm), affecting versions < 2026.2.22. It is fixed in 2026.2.22. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
- Which versions of openclaw are affected by GHSA-8MF7-VV8W-HJR2? openclaw (npm) versions < 2026.2.22 is affected.
- Is there a fix for GHSA-8MF7-VV8W-HJR2? Yes. GHSA-8MF7-VV8W-HJR2 is fixed in 2026.2.22. Upgrade to this version or later.
- Is GHSA-8MF7-VV8W-HJR2 exploitable, and should I be worried? Whether GHSA-8MF7-VV8W-HJR2 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
- What actually determines whether GHSA-8MF7-VV8W-HJR2 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.
- How do I fix GHSA-8MF7-VV8W-HJR2? Upgrade
openclawto 2026.2.22 or later.