OpenClaw's tools.exec.safeBins trusted PATH directories allowed binary shadowing in allowlist mode
GHSA-qhrr-grqp-6x2g · published 2026-03-03
- Severity
- Medium
- CVSS score
- 6.9
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2026.2.22
This is an allowlist bypass in exec policy that can lead to command execution in the OpenClaw runtime context when allowlist mode relies on safe bins and an attacker can influence trusted binary locations.
Upgrade openclaw to 2026.2.22 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Stop trusting PATH-derived directories for safe-bin trust. Add explicit tools.exec.safeBinTrustedDirs for opt-in extra trusted paths. Pin safe-bin shell execution to resolved absolute executable paths.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| openclaw | npm | < 2026.2.22 | 2026.2.22 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalOpenClaw: QQBot admin commands could skip DM-only and allowFrom policyopenclaw
- CriticalOpenClaw: Feishu webhook and card-action validation now fail closedopenclaw
- CriticalOpenClaw: Gateway HTTP endpoints re-resolve bearer auth after SecretRef rotationopenclaw
- CriticalOpenClaw: Sandbox escape via TOCTOU race in remote FS bridge readFileopenclaw
- CriticalOpenClaw: Heartbeat context inheritance bypasses sandbox via senderIsOwner escalationopenclaw
- CriticalOpenClaw has a CWD `.env` environment variable injection which bypasses host-env policy and allows config takeoveropenclaw
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.