CVE-2026-32009: OpenClaw · safeBins static default trusted dirs allow writable-dir binary hijack (`jq`)
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 5.7 Medium : upgrade to 2026.2.24 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.2.24
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.2.24.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in OpenClaw version 2026.2.24 which restricts default safe-bin trusted directories to immutable system paths and requires explicit opt-in for package-manager or user-managed paths. Users should upgrade to version 2026.2.24 or later to remediate this vulnerability. No additional mitigation is required once patched.
Description
OpenClaw CLI versions up to 2026.2.23 have a vulnerability in the safeBins allowlist policy where static default trusted directories include writable package-manager paths like /opt/homebrew/bin and /usr/local/bin. An attacker with write access to these directories can place a malicious binary with the same name as a trusted executable (e.g., jq), causing OpenClaw to execute the attacker-controlled binary. This allows command execution within the OpenClaw runtime context. The issue is fixed in version 2026.2.24 by restricting trusted directories to immutable system paths and requiring explicit opt-in for user-managed paths.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-5gj7-jf77-q2q2 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-32009 (opens in a new tab)
- github.com/openclaw/openclaw/commit/b67e600bff696ff2ed9b470826590c0ce6b3bb0a (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- vulncheck.com/advisories/openclaw-binary-hijacking-via-static-default-trusted-directories-in-safebins (opens in a new tab)