Summary
OpenClaw's tools.exec.safeBins trusted PATH directories allowed binary shadowing in allowlist mode
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.
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.
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.
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 versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
- Stop trusting PATH-derived directories for safe-bin trust.
- Add explicit
tools.exec.safeBinTrustedDirsfor opt-in extra trusted paths. - Pin safe-bin shell execution to resolved absolute executable paths.
Frequently Asked Questions
- What is GHSA-QHRR-GRQP-6X2G? GHSA-QHRR-GRQP-6X2G is a medium-severity security vulnerability in openclaw (npm), affecting versions < 2026.2.22. It is fixed in 2026.2.22.
- Which versions of openclaw are affected by GHSA-QHRR-GRQP-6X2G? openclaw (npm) versions < 2026.2.22 is affected.
- Is there a fix for GHSA-QHRR-GRQP-6X2G? Yes. GHSA-QHRR-GRQP-6X2G is fixed in 2026.2.22. Upgrade to this version or later.
- Is GHSA-QHRR-GRQP-6X2G exploitable, and should I be worried? Whether GHSA-QHRR-GRQP-6X2G 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
- What actually determines whether GHSA-QHRR-GRQP-6X2G 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.
- How do I fix GHSA-QHRR-GRQP-6X2G? Upgrade
openclawto 2026.2.22 or later.