How severe is GHSA-qhrr-grqp-6x2g?

No CVSS score has been assigned to GHSA-qhrr-grqp-6x2g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qhrr-grqp-6x2g?

GHSA-qhrr-grqp-6x2g affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-qhrr-grqp-6x2g?

Update openclaw to 2026.2.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qhrr-grqp-6x2g is resolved across your whole dependency graph.

How do I detect GHSA-qhrr-grqp-6x2g in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qhrr-grqp-6x2g if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-qhrr-grqp-6x2g actively exploited in the wild?

No public exploit code has been indexed for GHSA-qhrr-grqp-6x2g yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-qhrr-grqp-6x2g published, and has it been updated?

GHSA-qhrr-grqp-6x2g was published on March 3, 2026 and was last updated on March 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

OpenClaw's tools.exec.safeBins trusted PATH directories allowed binary shadowing in allowlist modeGHSA-qhrr-grqp-6x2g

Fix: openclaw/openclaw@64b273a

GHSA-qhrr-grqp-6x2g is a security vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 4, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

2.4Mdownloads / week

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 Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.22`npm install openclaw@2026.2.22`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qhrr-grqp-6x2g is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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) - L

O3 Security · Impact-Aware SCA

Is GHSA-qhrr-grqp-6x2g in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works