Most recent entries from all

bdu:2026-05006

2026-10-01T04:12:02.977442+00:00

bdu:2026-05006

BREW-openclaw-cli-CVE-2026-31997 — OpenClaw: system.run approvals did not bind PATH-token executable identity, enabling post-approval executable rebind

2026-10-01T04:12:02.977526+00:00

Affected: Homebrew: openclaw-cli

### 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`

fkie_cve-2026-31997

2026-10-01T04:12:02.977606+00:00

OpenClaw versions prior to 2026.3.1 fail to pin executable identity for non-path-like argv[0] tokens in system.run approvals, allowing post-approval executable rebind attacks. Attackers can modify PATH resolution after approval to execute a different binary than the operator approved, enabling arbitrary command execution.

GHSA-q399-23r3-hfx4 — OpenClaw: system.run approvals did not bind PATH-token executable identity, enabling post-approval executable rebind

2026-10-01T04:12:02.977652+00:00

Affected: npm: openclaw

### 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`