How severe is GHSA-6pfc-6m7w-m8fx?

GHSA-6pfc-6m7w-m8fx has a CVSS score of 7.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6pfc-6m7w-m8fx?

GHSA-6pfc-6m7w-m8fx affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-6pfc-6m7w-m8fx?

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

How do I detect GHSA-6pfc-6m7w-m8fx 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-6pfc-6m7w-m8fx 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-6pfc-6m7w-m8fx?

O3 pinpoints whether GHSA-6pfc-6m7w-m8fx 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-6pfc-6m7w-m8fx actively exploited in the wild?

No public exploit code has been indexed for GHSA-6pfc-6m7w-m8fx 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 type of vulnerability is GHSA-6pfc-6m7w-m8fx?

GHSA-6pfc-6m7w-m8fx is classified as CWE-807 (CWE-807). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6pfc-6m7w-m8fx published, and has it been updated?

GHSA-6pfc-6m7w-m8fx was published on March 31, 2026 and was last updated on April 28, 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-6pfc-6m7w-m8fx

HIGH

GHSA-6pfc-6m7w-m8fx is a high-severity (CVSS 7.3) CWE-807 vulnerability in openclaw. O3 Security confirms whether GHSA-6pfc-6m7w-m8fx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw has a gateway exec allowlist allow-always bypass via unregistered /usr/bin/script wrapper

Also known asCVE-2026-41390

Published

Mar 31, 2026

Updated

Apr 28, 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.2Mdownloads / week

Description

Summary

Allow-always persistence did not unwrap /usr/bin/script and similar wrappers to the actual executed target before storing trust decisions.

Impact

A user approval for one wrapped command could persist trust for a wrapper binary that later executed a different underlying program.

Affected Component

src/infra/dispatch-wrapper-resolution.ts, src/infra/exec-wrapper-resolution.ts

Fixed Versions

Affected: <= 2026.3.24
Patched: >= 2026.3.28
Latest stable 2026.3.28 contains the fix.

Fix

Fixed by commit 83da3cfe31 (infra: unwrap script wrapper approval targets).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.3.28

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

Frequently Asked Questions

## Summary Allow-always persistence did not unwrap `/usr/bin/script` and similar wrappers to the actual executed target before storing trust decisions. ## Impact A user approval for one wrapped command could persist trust for a wrapper binary that later executed a different underlying program. ## Affected Component `src/infra/dispatch-wrapper-resolution.ts, src/infra/exec-wrapper-resolution.ts` ## Fixed Versions - Affected: `<= 2026.3.24` - Patched: `>= 2026.3.28` - Latest stable `2026.3.28` contains the fix. ## Fix Fixed by commit `83da3cfe31` (`infra: unwrap script wrapper approval

O3 Security · Impact-Aware SCA

Is GHSA-6pfc-6m7w-m8fx in your dependencies?

O3 detects GHSA-6pfc-6m7w-m8fx 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