Openclaw cli: OpenClaw's tools.exec.safeBins trusted PATH directories allowed binary shadowing in allowlist mode
Affects openclaw-cliSource GCVE Database
CVSS 6.9 Medium : upgrade to 2026.7.1 when convenient.
Data as of 17 Nov 2026, 19:05 UTC
- Patch
- Available – fixed in 2026.7.1
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NWhat to do
Upgrade openclaw-cli to 2026.7.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and planned for release in version 2026.2.22. Users should upgrade to this version once released. The fix removes trust in PATH-derived directories for safe-bin resolution, requires explicit configuration of trusted directories, and ensures execution uses absolute resolved paths. If you cannot patch yet, users should avoid relying on allowlist mode with safeBins in environments where untrusted binaries could be placed in PATH directories.
Description
OpenClaw CLI in allowlist mode trusted PATH-derived directories for safe binary execution, allowing an attacker to bypass the allowlist by placing a same-name binary in a trusted directory. This could lead to command execution within the OpenClaw runtime context. The vulnerability affects openclaw versions up to 2026.2.21-2 and is planned to be fixed in version 2026.2.22. The root cause is trusting PATH-derived directories instead of explicit trusted directories and using shell command tokens that could resolve to shadowed binaries.