AI agent vulnerability · OpenClaw

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

highCVSS 4.0 8.7GHSA-q399-23r3-hfx4

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.

Published Mar 2, 2026 · Updated Mar 19, 2026

Affected packages

openclaw

Ecosystem: npm
Affected: < 2026.3.1
Fixed in: 2026.3.1
Check: npm ls openclaw

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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

Credited to tdjackey.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More OpenClaw vulnerabilities

All OpenClaw entries