How severe is GHSA-p4x4-2r7f-wjxg?

GHSA-p4x4-2r7f-wjxg has a CVSS score of 7.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-p4x4-2r7f-wjxg?

GHSA-p4x4-2r7f-wjxg affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-p4x4-2r7f-wjxg?

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

How do I detect GHSA-p4x4-2r7f-wjxg 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-p4x4-2r7f-wjxg 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-p4x4-2r7f-wjxg?

O3 pinpoints whether GHSA-p4x4-2r7f-wjxg 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-p4x4-2r7f-wjxg actively exploited in the wild?

No public exploit code has been indexed for GHSA-p4x4-2r7f-wjxg 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-p4x4-2r7f-wjxg?

GHSA-p4x4-2r7f-wjxg 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-p4x4-2r7f-wjxg published, and has it been updated?

GHSA-p4x4-2r7f-wjxg was published on April 1, 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

Not in CISA KEV

HIGH severity

GHSA-p4x4-2r7f-wjxg

HIGHFix: openclaw/openclaw@9ec44fa

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

OpenClaw gateway exec allow-always over-trusts positional carrier executables

Also known asCVE-2026-41380

Published

Apr 1, 2026

Updated

Apr 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Apr 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

openclawnpm

3.1Mdownloads / week

Description

Summary

Allow-always persistence could trust wrapper carrier executables instead of the actual invoked target when commands were routed through dispatch wrappers.

Impact

A one-time approval could persist a broader future allowlist entry than the operator intended, weakening execution approval boundaries.

Affected Component

src/infra/exec-approvals-allowlist.ts

Fixed Versions

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

Fix

Fixed by commit 9ec44fad39 (Exec approvals: reject wrapper carrier allow-always 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-p4x4-2r7f-wjxg 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-p4x4-2r7f-wjxg 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-p4x4-2r7f-wjxg. 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 could trust wrapper carrier executables instead of the actual invoked target when commands were routed through dispatch wrappers. ## Impact A one-time approval could persist a broader future allowlist entry than the operator intended, weakening execution approval boundaries. ## Affected Component `src/infra/exec-approvals-allowlist.ts` ## Fixed Versions - Affected: `<= 2026.3.24` - Patched: `>= 2026.3.28` - Latest stable `2026.3.28` contains the fix. ## Fix Fixed by commit `9ec44fad39` (`Exec approvals: reject wrapper carrier allow-always targets`).

O3 Security · Impact-Aware SCA

Is GHSA-p4x4-2r7f-wjxg in your dependencies?

O3 detects GHSA-p4x4-2r7f-wjxg 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