GitHub Advisoryadvisory · npm

GHSA-5gj7-jf77-q2q2 OpenClaw: safeBins static default trusted dirs allow writable-dir binary hijack (`jq`)

HIGH Published 2026-03-03 Modified 2026-03-30 Official page ↗
Aliases
CVE-2026-32009
Ecosystem
npm
Packages
openclaw
Severity
High
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H
Weaknesses
CWE-426, CWE-428, CWE-829
Reviewed
2026-03-03

Affected packages

• npm openclaw: < 2026.2.24 → fixed in 2026.2.24

Description

Summary In `openclaw= 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) `[email protected]` is published on npm and contains the fix commit(s) listed above. This advisory now marks `>= 2026.2.24` as patched.

Related

Alias · CVE (1)

  • CVE-2026-32009 OpenClaw versions prior to 2026.2.24 contain a policy bypass vulnerability in the safeBins allowlist evaluation that trusts static default… vulnerability

Weakness · CWE (3)

  • CWE-426 Untrusted Search Path weakness
  • CWE-428 Unquoted Search Path or Element weakness
  • CWE-829 Inclusion of Functionality from Untrusted Control Sphere weakness

References