high8.7
CVE-2026-31997
OpenClaw: system.run approvals did not bind PATH-token executable identity, enabling post-approval executable rebind
Impact
### Summary For `host=node` runs, approvals validated command context but did not pin executable identity for non-path-like `argv[0]` tokens (for example `tr`). If PATH resolution changed after approval, execution could run a different binary. ### Impact A previously approved action could execute a different executable than the operator approved. ### Fix Node `system.run` approvals now require immutable `systemRunPlan` data, and path-token commands are pinned to canonical executable identity (`realpath`) across approval and execution. ### Affected and Patched Versions - Affected: `<= 2026.2.26` - Patched: `2026.3.1`
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| npm | openclaw | < 2026.3.1 | 2026.3.1 |
Affected products
| Vendor | Product | Affected versions |
|---|---|---|
| Openclaw | Openclaw | before 2026.3.1 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/openclaw/openclaw/security/advisories/GHSA-q399-23r3-hfx4
- https://www.vulncheck.com/advisories/openclaw-executable-rebind-via-unbound-path-token-in-system-run-approvals
- https://github.com/advisories/GHSA-q399-23r3-hfx4
- https://nvd.nist.gov/vuln/detail/CVE-2026-31997