Every CVESearch/Get API key

GHSA-qhrr-grqp-6x2g

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

6.9 MediumFix available

GHSA-qhrr-grqp-6x2g is a medium vulnerability (CVSS 6.9) in openclaw, published March 3, 2026. No source lists public exploit code. Fixed in openclaw 2026.2.22.

What does this mean?
Severity
6.9 MediumCVSS 4.0, GitHub Advisories
Exploit chance
UnscoredNo EPSS score yet
Exploitation
None knownNot on CISA’s or ENISA’s lists
Fixed in
2026.2.22openclaw

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.

Attack profile

How easy it is to exploit

Attack vector
Local
Complexity
Low
Privileges needed
None
User interaction
None

What an attacker can affect

Confidentiality
None
Integrity
High
Availability
None

Affected packages

Affected packages
PackageAffectedFixed
openclaw
npm
before 2026.2.22
2026.2.22

What each source reports

GitHub Advisories Score used6.9

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

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.

Record
GHSA-qhrr-grqp-6x2g
CVSS 4.0
6.9 MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Weakness
CWE-426
Updated
2026-11-02
OSV6.9

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

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.

Record
GHSA-qhrr-grqp-6x2g
CVSS 4.0
6.9 MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Weakness
CWE-426
Updated
2026-11-02

History

History
RecordedChangedSources
first indexedGitHub Advisories, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

References

MoveEnter Open