GitHub Advisoryadvisory · npm
GHSA-8mf7-vv8w-hjr2 OpenClaw's tools.exec.safeBins generic fallback allowed interpreter-style inline payload execution in allowlist mode
LOW
Official page ↗
- Ecosystem
- npm
- Packages
- openclaw
- Severity
- Low
- CVSS vector
- CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
- Weaknesses
- CWE-693, CWE-78
- Reviewed
- 2026-03-03
Affected packages
• npm openclaw: < 2026.2.22 → fixed in 2026.2.22
Description
Summary
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.22` (planned next npm release)
Fix
• Remove generic safe-bin fallback during allowlist evaluation.
• Require explicit safe-bin profiles for `safeBins` entries.
• Add configurable `tools.exec.safeBinProfiles` (global + per-agent) for safe custom binaries.
• Update docs to clearly separate `safeBins` from command allowlist semantics.
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.