How severe is GHSA-g75x-8qqm-2vxp?

GHSA-g75x-8qqm-2vxp has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-g75x-8qqm-2vxp?

GHSA-g75x-8qqm-2vxp affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-g75x-8qqm-2vxp?

Update openclaw to 2026.2.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g75x-8qqm-2vxp is resolved across your whole dependency graph.

How do I detect GHSA-g75x-8qqm-2vxp 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-g75x-8qqm-2vxp 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-g75x-8qqm-2vxp?

O3 pinpoints whether GHSA-g75x-8qqm-2vxp 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-g75x-8qqm-2vxp actively exploited in the wild?

No public exploit code has been indexed for GHSA-g75x-8qqm-2vxp 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-g75x-8qqm-2vxp?

GHSA-g75x-8qqm-2vxp has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 3th 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-g75x-8qqm-2vxp published, and has it been updated?

GHSA-g75x-8qqm-2vxp 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-g75x-8qqm-2vxp

HIGH

OpenClaw's `tools.exec.safeBins` PATH-hijack allowed trojan binaries to bypass allowlist checks

Also known asCVE-2026-32015

Published

Mar 3, 2026

Updated

Mar 30, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk3th percentile+0.11%

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

3.7Mdownloads / week

Description

Summary

tools.exec.safeBins allowlist checks could be bypassed by PATH-hijacked binaries, allowing execution of attacker-controlled trojan binaries under an allowlisted executable name.

Affected Packages / Versions

Package: openclaw (npm)
Latest published version at triage time: 2026.2.17
Affected range: >= 2026.1.21 < 2026.2.18
Patched version: 2026.2.19

Impact

In allowlist mode, safeBins validation previously accepted a resolved executable path based on executable name and argument shape, without enforcing trusted executable directories. If an attacker could influence process PATH resolution before gateway startup (or otherwise control the gateway launch environment), a trojan binary with an allowlisted name (for example jq) could be executed.

Severity Rationale

This issue is rated medium because exploitation requires an additional precondition: influencing the gateway process PATH / launch environment. Request-scoped PATH injection is blocked for host execution.

Fix

safeBins now requires the resolved executable path to come from trusted bin directories (system defaults plus gateway startup PATH), closing the bypass.

Fix Commit(s)

28bac46c92069dc728524fbf383024c1b64e5c23

OpenClaw thanks @jackhax for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.1.21&&< 2026.2.19	2026.2.19

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.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g75x-8qqm-2vxp 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-g75x-8qqm-2vxp 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-g75x-8qqm-2vxp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary `tools.exec.safeBins` allowlist checks could be bypassed by PATH-hijacked binaries, allowing execution of attacker-controlled trojan binaries under an allowlisted executable name. ## Affected Packages / Versions - Package: `openclaw` (npm) - Latest published version at triage time: `2026.2.17` - Affected range: `>= 2026.1.21 < 2026.2.18` - Patched version: `2026.2.19` ## Impact In allowlist mode, `safeBins` validation previously accepted a resolved executable path based on executable name and argument shape, without enforcing trusted executable directories. If an attacker could

O3 Security · Impact-Aware SCA

Is GHSA-g75x-8qqm-2vxp in your dependencies?

O3 detects GHSA-g75x-8qqm-2vxp 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