OpenClaw Vulnerability: Insecure Executable Rebinding in system.run Approvals
Summary
GHSA-q399-23r3-hfx4: For host=node runs, approvals validated command context but did not pin executable identity for non-path-like argv[0] tokens (for example tr). Affects openclaw versions < 2026.3.1. Fixed in 2026.3.1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
OpenClaw is an open-source package designed for executing system commands in a controlled environment. It allows users to run commands on a host machine while validating the command context to ensure security. However, a recent vulnerability has been identified that affects the integrity of command execution, particularly when using the system.run feature.
Vulnerability Detail
The vulnerability arises from the fact that for host=node runs, the approvals for system.run commands validated the command context but did not bind the executable identity for non-path-like argv[0] tokens. This means that if the PATH resolution changed after the approval, the execution could run a different binary than the one originally approved by the operator. This could lead to unauthorized command execution, posing a significant security risk.
How To Fix
Latest published version: 2026.10.6 as of 22 Oct 2026
npm install openclaw@2026.10.6Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2026.3.1
This is the first release that contains the fix.
npm install openclaw@2026.3.1Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, users can manually verify the executable identity of commands before executing them, ensuring that the correct binary is being run. However, this is not a long-term solution and updating to the patched version is strongly recommended.
Conclusion
The OpenClaw vulnerability presents a significant risk due to the potential for unauthorized command execution. It is crucial for users to update to the patched version 2026.3.1 to mitigate this risk. Additionally, utilizing tools like Vulert can help in monitoring and managing vulnerabilities in open-source packages effectively.
See every vulnerability recorded for openclaw →
FAQ
The CVSS score of this vulnerability is 8.7, indicating a high severity level.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If exploited, this vulnerability could allow an attacker to execute unauthorized commands on the host machine, leading to potential data breaches or system compromise.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.
If you cannot update immediately, ensure to review and validate the executables being run manually to mitigate the risk until you can apply the patch.
References
Related vulnerabilities
Recent vulnerabilities recorded for openclaw.
