GHSA-q399-23r3-hfx4High

OpenClaw: system.run approvals did not bind PATH-token executable identity, enabling post-approval executable rebind

Published
March 2, 2026
Last Modified
March 19, 2026

🔗 CVE IDs covered (1)

CVE-2026-31997 →

📋 Description

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 products1

  • npm/openclaw:< 2026.3.1

🔗 References (4)