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.
openclaw (npm)<= 2026.2.21-2>= 2026.2.22 (planned next npm release)safeBins entries.tools.exec.safeBinProfiles (global + per-agent) for safe custom binaries.safeBins from command allowlist semantics.47c3f742b6c488be26dd7b9636dbbb8676089154patched_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.
{
"cwe_ids": [
"CWE-693",
"CWE-78"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-03T23:05:35Z",
"nvd_published_at": null,
"severity": "LOW"
}