GHSA-qhrr-grqp-6x2g

OpenClaw's tools.exec.safeBins trusted PATH directories allowed binary shadowing in allowlist mode

Medium npm

Severity: 0.0 / 10; Medium · CVSS 4.0
Exploit chance (EPSS): —; No score published
Known exploited: No; Not in CISA's catalog
Weakness: CWE-426 Untrusted Search Path
Fix: 2026.2.22; Upgrade openclaw to this version or later

Description

Summary

In openclaw allowlist mode, tools.exec.safeBins trusted PATH-derived directories for safe-bin resolution. A same-name binary placed in a trusted PATH directory could satisfy safe-bin checks and execute.

Impact

This is an allowlist bypass in exec policy that can lead to command execution in the OpenClaw runtime context when allowlist mode relies on safe bins and an attacker can influence trusted binary locations.

Affected Packages / Versions

Package: openclaw (npm)
Vulnerable versions: <= 2026.2.21-2
Patched versions: >= 2026.2.22 (planned next release)
Latest published npm version at triage time (2026-02-22): 2026.2.21-2

Root Cause

Safe-bin trust accepted PATH-derived directories instead of explicit trusted directories.
Safe-bin execution used shell command tokens that could resolve to shadowed binaries.

Remediation

Stop trusting PATH-derived directories for safe-bin trust.
Add explicit tools.exec.safeBinTrustedDirs for opt-in extra trusted paths.
Pin safe-bin shell execution to resolved absolute executable paths.

Fix Commit(s)

64b273a71cf0b2f2419c974832cede1fc2158729

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.22). After npm release, this advisory is ready for publish without additional field edits.

OpenClaw thanks @tdjackey for reporting.

Affected versions

npm

Package	Vulnerable	Fixed in
openclaw	`< 2026.2.22`	`2026.2.22`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

openclaw npm → `2026.2.22`

npm

npm install openclaw@2026.2.22

yarn

yarn add openclaw@2026.2.22

pnpm

pnpm add openclaw@2026.2.22

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Attack vector: Local
Attack complexity: Low
Attack requirements: None
Privileges required: None
User interaction: None
Confidentiality (vulnerable system): None
Integrity (vulnerable system): High
Availability (vulnerable system): None
Confidentiality (subsequent systems): None
Integrity (subsequent systems): None
Availability (subsequent systems): None

Weakness

CWE-426: Untrusted Search Path

The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control.

How to prevent it

Architecture and Design, Implementation: Hard-code the search path to a set of known-safe values (such as system directories), or only allow them to be specified by the administrator in a configuration file. Do not allow these settings to be modified by an external party. Be careful to avoid related weaknesses such as CWE-426 and CWE-428.
Implementation: When invoking other programs, specify those programs using fully-qualified pathnames. While this is an effective approach, code that uses fully-qualified pathnames might not be portable to other systems that do not use the same pathnames. The portability can be improved by locating the full-qualified paths in a centralized, easily-modifiable location within the source code, and having the code refer to these paths.
Implementation: Remove or restrict all environment settings before invoking other programs. This includes the PATH environment variable, LD_LIBRARY_PATH, and other settings that identify the location of code libraries, and any application-specific search paths.
Implementation: Check your search path before use and remove any elements that are likely to be unsafe, such as the current working directory or a temporary files directory.
Implementation: Use other functions that require explicit paths. Making use of any of the other readily available functions that require explicit paths is a safe way to avoid this problem. For example, system() in C does not require a full path since the shell can take care of it, while execl() and execv() require a full path.

References

Packages

github.com/openclaw/openclaw

Timeline

Mar 3, 2026 Published
Mar 4, 2026 Last updated by the source

Advisory	Severity	Why it's related
GHSA-3x84-qq85-fj65 OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs	High	Also affects openclaw
GHSA-9c3v-684m-579c OpenClaw MCP SSE redirects could forward Authorization headers	Medium	Also affects openclaw
GHSA-f397-5vjw-v2c2 OpenClaw: Shell inline-command parsing could miss an allowlist check	High	Also affects openclaw
GHSA-rx78-29qr-5hq8 OpenClaw: Workspace-derived service PATH could influence trash command selection	High	Also affects openclaw
GHSA-ccwh-wwpp-6wg5 OpenClaw: Host environment sanitizer missed two Node.js control variables	High	Also affects openclaw
GHSA-985f-72mj-8gf7 OpenClaw: Tool group policy callers could accept unvalidated group IDs	Medium	Also affects openclaw
GHSA-9v8j-9c9g-w66c OpenClaw: Bootstrap token replay could widen pending pairing scopes	Medium	Also affects openclaw
GHSA-c226-q6fx-6j6c OpenClaw: macOS Swift exec allowlist missed combined POSIX inline flags	Medium	Also affects openclaw

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor