OpenClaw Vulnerability: Binary Hijack Risk in SafeBins Configuration
Summary
GHSA-5gj7-jf77-q2q2: OpenClaw: safeBins static default trusted dirs allow writable-dir binary hijack (jq). Affects openclaw versions < 2026.2.24. Fixed in 2026.2.24. 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 tool designed for executing commands in a secure environment. It utilizes a feature called safeBins to manage executable binaries, ensuring that only trusted binaries are run. However, a flaw in its configuration allows for potential exploitation through writable directories, posing a risk to users who rely on this functionality.
Vulnerability Detail
The vulnerability arises from OpenClaw's reliance on static default trusted directories, which include package-manager paths such as /opt/homebrew/bin and /usr/local/bin. This configuration allows an attacker to place a malicious binary with the same name as a trusted executable (e.g., jq) in these directories. When OpenClaw evaluates safeBins, it may execute the attacker-controlled binary instead of the legitimate one, leading to unauthorized command execution. The severity of this vulnerability is rated as high, with a CVSS score of 8.5, indicating significant risk if exploited.
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.2.24
This is the first release that contains the fix.
npm install openclaw@2026.2.24Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, users can manually remove any writable directories from the safeBins configuration or ensure that no malicious binaries are placed in the trusted directories. This can be done by checking the contents of /opt/homebrew/bin and /usr/local/bin for any unauthorized binaries.
Conclusion
The OpenClaw vulnerability presents a significant risk due to its reliance on potentially writable directories for trusted binaries. Users are strongly advised to update to the patched version 2026.2.24 or later and implement recommended security practices to mitigate this risk.
See every vulnerability recorded for openclaw →
FAQ
The vulnerability allows for binary hijacking due to the inclusion of writable directories in the safeBins configuration.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If you cannot update, consider implementing the recommended workarounds to mitigate the risk until you can apply the patch.
SafeBins is a feature in OpenClaw that manages which binaries can be executed, relying on a trust model based on directory membership.
The CVSS score of this vulnerability is 8.5, indicating a high level of risk.
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.