Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-5gj7-jf77-q2q2
No affected components available
Summary
In openclaw<=2026.2.23, safe-bin trust in allowlist mode relied on static default trusted directories that included package-manager paths (notably /opt/homebrew/bin and /usr/local/bin).
When a same-name binary (for example jq) is placed in one of those trusted default directories, safe-bin evaluation can be satisfied and execute the attacker-controlled binary.
Impact
This is an exec allowlist safeBins policy bypass that can lead to command execution in the OpenClaw runtime context.
Severity is set to Medium given the required ability to write into trusted host binary directories.
Affected Packages / Versions
- Package:
openclaw(npm) - Vulnerable versions:
<= 2026.2.23 - Patched versions:
>= 2026.2.24(planned next npm release) - Latest published npm version at triage time (2026-02-24):
2026.2.23
Root Cause
- Default safe-bin trusted directories included package-manager/user-managed paths.
- Trust decision was directory-membership only for resolved executable paths.
Remediation
- Restrict default safe-bin trusted directories to immutable system paths:
/bin,/usr/bin. - Require explicit operator opt-in for package-manager/user paths via
tools.exec.safeBinTrustedDirs.
Fix Commit(s)
b67e600bff696ff2ed9b470826590c0ce6b3bb0a
Release Process Note
patched_versions is pre-set to the planned next release (2026.2.24).
Once npm release 2026.2.24 is published, this advisory should be ready for publish without additional version edits.
OpenClaw thanks @tdjackey for reporting.
Publication Update (2026-02-25)
openclaw@2026.2.24 is published on npm and contains the fix commit(s) listed above. This advisory now marks >= 2026.2.24 as patched.
The vulnerability requires local access to the device to be exploited. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker needs high-level or administrative privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the integrity of the data. There is a high impact on the availability of the system.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard