CVE-2026-32009

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.

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.

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.

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.

CVE-2026-32009 has a CVSS score of 5.7 (High). The vector is requires local access, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.24); upgrading removes the vulnerable code path.

Kodem intelligence

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

1. What is CVE-2026-32009? CVE-2026-32009 is a high-severity security vulnerability in openclaw (npm), affecting versions <= 2026.2.23. It is fixed in 2026.2.24.
2. How severe is CVE-2026-32009? CVE-2026-32009 has a CVSS score of 5.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-32009? openclaw (npm) versions <= 2026.2.23 is affected.
4. Is there a fix for CVE-2026-32009? Yes. CVE-2026-32009 is fixed in 2026.2.24. Upgrade to this version or later.
5. Is CVE-2026-32009 exploitable, and should I be worried? Whether CVE-2026-32009 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-32009 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-32009? Upgrade openclaw to 2026.2.24 or later.