PT-2026-25457 · Npm · Openclaw
Published
2026-03-03
·
Updated
2026-03-03
CVSS v3.1
7.8
High
| Vector | AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Summary
tools.exec.safeBins allowlist checks could be bypassed by PATH-hijacked binaries, allowing execution of attacker-controlled trojan binaries under an allowlisted executable name.Affected Packages / Versions
- Package:
openclaw(npm) - Latest published version at triage time:
2026.2.17 - Affected range:
>= 2026.1.21 < 2026.2.18 - Patched version:
2026.2.19
Impact
In allowlist mode,
safeBins validation previously accepted a resolved executable path based on executable name and argument shape, without enforcing trusted executable directories. If an attacker could influence process PATH resolution before gateway startup (or otherwise control the gateway launch environment), a trojan binary with an allowlisted name (for example jq) could be executed.Severity Rationale
This issue is rated
medium because exploitation requires an additional precondition: influencing the gateway process PATH / launch environment. Request-scoped PATH injection is blocked for host execution.Fix
safeBins now requires the resolved executable path to come from trusted bin directories (system defaults plus gateway startup PATH), closing the bypass.Fix Commit(s)
- 28bac46c92069dc728524fbf383024c1b64e5c23
OpenClaw thanks @jackhax for reporting.
Fix
Untrusted Search Path
Incorrect Authorization
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Openclaw