CVE-2026-32009: OpenClaw SafeBins Static Default Trusted Dirs Vulnerability

HIGH
Advisory Identifier: GHSA-5gj7-jf77-q2q2
CVSS 5.7
CWE-829 CWE-426 CWE-428
Published
Advisory Summary

CVE-2026-32009 is a HIGH (CVSS 5.7) safebins static default trusted dirs vulnerability (CWE-829: Inclusion of Functionality from Untrusted Control Sphere) affecting OpenClaw libraries in the npm ecosystem. The issue involves safebins static default trusted dirs allow writable-dir binary hijack (`jq`). Remediation is available by upgrading affected packages to version 2026.2.24.

CVE-2026-32009 at a Glance

CVE Identifier CVE-2026-32009
GHSA Identifier GHSA-5gj7-jf77-q2q2
Severity HIGH
CVSS v3.1 Base Score 5.7
CWE Classification CWE-829: Inclusion of Functionality from Untrusted Control Sphere
Affected Product OpenClaw
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 5.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity High (AC:H)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-32009

To remediate this vulnerability, upgrade all affected OpenClaw dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

openclaw fixed: 2026.2.24
npm install openclaw@2026.2.24
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls openclaw

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-32009, inspect your project dependencies using npm:

npm ls openclaw

Analyze the terminal output to locate any version of OpenClaw in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.2.24), your application is affected.

Note: The npm ls openclaw command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-829: Inclusion of Functionality from Untrusted Control Sphere, where the product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere. In OpenClaw, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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.

CVE-2026-32009 Affected OpenClaw Versions

1 component(s)
Fixed Versions:
2026.2.24
Product / Package Ecosystem Affected Versions Fixed Version
openclaw
npm
< 2026.2.24
2026.2.24

References

Frequently Asked Questions

What is CVE-2026-32009?
CVE-2026-32009 is a security vulnerability in OpenClaw involving safeBins static default trusted dirs allow writable-dir binary hijack (`jq`) under CWE-829: Inclusion of Functionality from Untrusted Control Sphere.
Which OpenClaw versions are affected?
Affected versions include releases prior to 2026.2.24 across affected packages: openclaw.
What version fixes CVE-2026-32009?
Upgrading to 2026.2.24 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openclaw affected?
Yes, openclaw is affected in releases prior to 2026.2.24. Upgrade your dependency to 2026.2.24 or later.
What is the CVSS score of CVE-2026-32009?
CVE-2026-32009 has a CVSS v3.1 base score of 5.7 (HIGH) with vector string CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H.
What CWE is associated with CVE-2026-32009?
CVE-2026-32009 is classified under CWE-829: Inclusion of Functionality from Untrusted Control Sphere (The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.).
How can I check npm dependencies for CVE-2026-32009?
Run the dependency tree command: 'npm ls openclaw'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5gj7-jf77-q2q2",
  "modified" : "2026-03-30T13:21:53Z",
  "published" : "2026-03-03T21:34:45Z",
  "aliases" : [ "CVE-2026-32009" ],
  "summary" : "OpenClaw: safeBins static default trusted dirs allow writable-dir binary hijack (`jq`)",
  "details" : "### Summary\nIn `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`).\nWhen 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.\n\n### Impact\nThis is an exec allowlist `safeBins` policy bypass that can lead to command execution in the OpenClaw runtime context.\nSeverity is set to Medium given the required ability to write into trusted host binary directories.\n\n### Affected Packages / Versions\n- Package: `openclaw` (npm)\n- Vulnerable versions: `<= 2026.2.23`\n- Patched versions: `>= 2026.2.24` (planned next npm release)\n- Latest published npm version at triage time (2026-02-24): `2026.2.23`\n\n### Root Cause\n- Default safe-bin trusted directories included package-manager/user-managed paths.\n- Trust decision was directory-membership only for resolved executable paths.\n\n### Remediation\n- Restrict default safe-bin trusted directories to immutable system paths: `/bin`, `/usr/bin`.\n- Require explicit operator opt-in for package-manager/user paths via `tools.exec.safeBinTrustedDirs`.\n\n### Fix Commit(s)\n- `b67e600bff696ff2ed9b470826590c0ce6b3bb0a`\n\n### Release Process Note\n`patched_versions` is pre-set to the planned next release (`2026.2.24`).\nOnce npm release `2026.2.24` is published, this advisory should be ready for publish without additional version edits.\n\nOpenClaw thanks @tdjackey for reporting.\n\n\n### Publication Update (2026-02-25)\n`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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "openclaw"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2026.2.24"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2026.2.23"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/security/advisories/GHSA-5gj7-jf77-q2q2"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-32009"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/commit/b67e600bff696ff2ed9b470826590c0ce6b3bb0a"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openclaw/openclaw"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/openclaw-binary-hijacking-via-static-default-trusted-directories-in-safebins"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-426", "CWE-428", "CWE-829" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-03T21:34:45Z",
    "nvd_published_at" : "2026-03-19T22:16:33Z"
  }
}