How severe is GHSA-4gc7-qcvf-38wg?

GHSA-4gc7-qcvf-38wg has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-4gc7-qcvf-38wg?

GHSA-4gc7-qcvf-38wg affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-4gc7-qcvf-38wg?

Update openclaw to 2026.2.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4gc7-qcvf-38wg is resolved across your whole dependency graph.

How do I detect GHSA-4gc7-qcvf-38wg 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-4gc7-qcvf-38wg 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-4gc7-qcvf-38wg?

O3 pinpoints whether GHSA-4gc7-qcvf-38wg 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-4gc7-qcvf-38wg actively exploited in the wild?

No public exploit code has been indexed for GHSA-4gc7-qcvf-38wg 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.

What is the EPSS score for GHSA-4gc7-qcvf-38wg?

GHSA-4gc7-qcvf-38wg has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 20th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-4gc7-qcvf-38wg published, and has it been updated?

GHSA-4gc7-qcvf-38wg was published on March 3, 2026 and was last updated on March 30, 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-4gc7-qcvf-38wg

HIGH

In OpenClaw, manually adding sort to tools.exec.safeBins could bypass allowlist approval via --compress-program

Also known asCVE-2026-32010

Published

Mar 3, 2026

Updated

Mar 30, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk20th percentile+0.24%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

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

openclawnpm

4.3Mdownloads / week

Description

Summary

This issue applies to a non-default configuration only. If sort is manually added to tools.exec.safeBins, OpenClaw could treat sort --compress-program=<prog> as valid safe-bin usage. In security=allowlist + ask=on-miss, this could satisfy allowlist checks and skip operator approval, while GNU sort may invoke an external program via --compress-program.

Affected Packages / Versions

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

Default Installations

Default installs are not impacted by this specific path because sort is not included in default tools.exec.safeBins.

Impact

Type: approval/allowlist bypass in optional safe-bin configuration
Scope: deployments that explicitly include sort in tools.exec.safeBins and use allowlist + ask=on-miss
Consequence: an external program may run under the OpenClaw process context without expected approval

Technical Details

sort safe-bin profile allowed --compress-program as a value flag.
Safe-bin satisfaction could therefore mark allowlist checks as satisfied.
In ask=on-miss, satisfied allowlist checks skip approval prompts.

Fix

Block --compress-program in safe-bin sort policy.
Add unit and e2e regression coverage for sort --compress-program denial in safe-bin mode.

Fix Commit(s)

57fbbaebca4d34d17549accf6092ae26eb7b605c

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-4gc7-qcvf-38wg 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-4gc7-qcvf-38wg 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-4gc7-qcvf-38wg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary This issue applies to a **non-default configuration** only. If `sort` is manually added to `tools.exec.safeBins`, OpenClaw could treat `sort --compress-program=<prog>` as valid safe-bin usage. In `security=allowlist` + `ask=on-miss`, this could satisfy allowlist checks and skip operator approval, while GNU `sort` may invoke an external program via `--compress-program`. ### Affected Packages / Versions - Ecosystem: npm - Package: `openclaw` - Affected: `<= 2026.2.21-2` - Patched (planned next release): `>= 2026.2.22` ### Default Installations Default installs are not impacted by t

O3 Security · Impact-Aware SCA

Is GHSA-4gc7-qcvf-38wg in your dependencies?

O3 detects GHSA-4gc7-qcvf-38wg 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