In openclaw@2026.2.24, approval-bound system.run on node hosts could be influenced by mutable symlink cwd targets between approval and execution.
Approval matching on the gateway validated command/argv and binding fields, including cwd, as provided text. Node execution later used runtime cwd resolution. A symlinked cwd could therefore be retargeted after approval and before spawn.
OpenClaw's trust model does not treat one shared gateway as a multi-tenant adversarial boundary, but approval integrity is still a security boundary for operator-reviewed command execution.
openclaw (npm)<= 2026.2.24>= 2026.2.25f789f880c934caa8be25b38832f27f90f37903dbThe fix adds defense-in-depth hardening for approval-bound node execution:
cwd paths for approval-bound system.runcommandArgvPatched version is pre-set to the release (2026.2.25). Advisory published with npm release 2026.2.25.
OpenClaw thanks @tdjackey for reporting.
{
"cwe_ids": [
"CWE-367",
"CWE-59"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-03T19:18:06Z",
"nvd_published_at": null,
"severity": "MODERATE"
}