Approval Integrity Bypass in OpenClaw: Execute Unexpected Binaries
Summary
GHSA-mxmg-3p7m-2ghr: Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-hwpq-rrpf-pgcq. Affects openclaw versions < 2026.2.24. No fix is published. 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 commands in a controlled environment. It allows users to run system commands while maintaining a level of security through approval contexts. However, certain versions of OpenClaw are vulnerable to an integrity bypass that can lead to unauthorized command execution, compromising the security of the system.
Vulnerability Detail
The vulnerability arises from an approval-integrity bypass in OpenClaw versions prior to 2026.2.25. The issue occurs in the system.run function, where the command text displayed for approval is manipulated by trimming whitespace from the argv tokens. This allows an attacker to craft a malicious executable with trailing spaces, leading to the execution of a different binary than intended. As a result, unauthorized commands can be executed under the OpenClaw runtime user, especially if the attacker can influence the command arguments and reuse an approval context.
How To Fix
No fixed version is published for this vulnerability.
To fix this vulnerability, update OpenClaw to version 2026.2.25 or later. You can do this by running the following command in your terminal: npm install openclaw@latest. This will ensure that you are using the patched version that addresses the integrity bypass issue.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, avoid using the system.run function with user-provided command arguments until you can update to the patched version. Ensure that any command execution is strictly controlled and validated to prevent unauthorized access.
Conclusion
The OpenClaw package has a significant vulnerability that allows for an approval integrity bypass, potentially leading to unauthorized command execution. It is crucial to update to the latest version to mitigate this risk. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.
See every vulnerability recorded for openclaw →
FAQ
The CVSS score of this vulnerability is 4.8, indicating a moderate level of risk.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can provide real-time alerts. You can also check your application using the Vulert playground without any signup.
OpenClaw versions prior to 2026.2.25 are affected by this vulnerability.
If you cannot update immediately, avoid using the vulnerable functionality and ensure that command execution is tightly controlled.
While the primary risk is unauthorized command execution, which could lead to various security issues, the specific impact on data loss would depend on the commands executed by an attacker.
References
Related vulnerabilities
Recent vulnerabilities recorded for openclaw.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.