Summary
OpenClaw: system.run approvals did not bind PATH-token executable identity, enabling post-approval executable rebind
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.
Affected and Patched Versions
- Affected:
<= 2026.2.26 - Patched:
2026.3.1
Impact
A previously approved action could execute a different executable than the operator approved.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Node system.run approvals now require immutable systemRunPlan data, and path-token commands are pinned to canonical executable identity (realpath) across approval and execution.
Frequently Asked Questions
- What is CVE-2026-31997? CVE-2026-31997 is a high-severity security vulnerability in openclaw (npm), affecting versions < 2026.3.1. It is fixed in 2026.3.1.
- Which versions of openclaw are affected by CVE-2026-31997? openclaw (npm) versions < 2026.3.1 is affected.
- Is there a fix for CVE-2026-31997? Yes. CVE-2026-31997 is fixed in 2026.3.1. Upgrade to this version or later.
- Is CVE-2026-31997 exploitable, and should I be worried? Whether CVE-2026-31997 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-31997 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-31997? Upgrade
openclawto 2026.3.1 or later.