How severe is GHSA-8mf7-vv8w-hjr2?

No CVSS score has been assigned to GHSA-8mf7-vv8w-hjr2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8mf7-vv8w-hjr2?

GHSA-8mf7-vv8w-hjr2 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-8mf7-vv8w-hjr2?

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

How do I detect GHSA-8mf7-vv8w-hjr2 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-8mf7-vv8w-hjr2 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.

How does O3 Security protect against GHSA-8mf7-vv8w-hjr2?

O3 pinpoints whether GHSA-8mf7-vv8w-hjr2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-8mf7-vv8w-hjr2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8mf7-vv8w-hjr2 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-8mf7-vv8w-hjr2 published, and has it been updated?

GHSA-8mf7-vv8w-hjr2 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

GHSA-8mf7-vv8w-hjr2

OpenClaw's tools.exec.safeBins generic fallback allowed interpreter-style inline payload execution in allowlist mode

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

3.7Mdownloads / week

Description

Summary

When tools.exec.safeBins contained a binary without an explicit safe-bin profile, OpenClaw used a permissive generic fallback profile. In allowlist mode, that could let interpreter-style binaries (for example python3, node, ruby) execute inline payloads via flags like -c.

This requires explicit operator configuration to add such binaries to safeBins, so impact is limited to non-default/misconfigured deployments.

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.2.21-2
Patched in code: >= 2026.2.22 (planned next npm release)

Fix

Remove generic safe-bin fallback during allowlist evaluation.
Require explicit safe-bin profiles for safeBins entries.
Add configurable tools.exec.safeBinProfiles (global + per-agent) for safe custom binaries.
Update docs to clearly separate safeBins from command allowlist semantics.

Fix Commit(s)

47c3f742b6c488be26dd7b9636dbbb8676089154

Release Process Note

patched_versions is pre-set to the planned next release (>= 2026.2.22) so once that npm release is published, the advisory can be published directly without further metadata edits.

OpenClaw thanks @tdjackey for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.2.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8mf7-vv8w-hjr2 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.
How O3 protects you
O3 pinpoints whether GHSA-8mf7-vv8w-hjr2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8mf7-vv8w-hjr2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary When `tools.exec.safeBins` contained a binary without an explicit safe-bin profile, OpenClaw used a permissive generic fallback profile. In allowlist mode, that could let interpreter-style binaries (for example `python3`, `node`, `ruby`) execute inline payloads via flags like `-c`. This requires explicit operator configuration to add such binaries to `safeBins`, so impact is limited to non-default/misconfigured deployments. ### Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `<= 2026.2.21-2` - Patched in code: `>= 2026.2.22` (planned next npm release

O3 Security · Impact-Aware SCA

Is GHSA-8mf7-vv8w-hjr2 in your dependencies?

O3 detects GHSA-8mf7-vv8w-hjr2 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works