How severe is GHSA-2cq5-mf3v-mx44?

GHSA-2cq5-mf3v-mx44 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-2cq5-mf3v-mx44?

GHSA-2cq5-mf3v-mx44 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-2cq5-mf3v-mx44?

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

How do I detect GHSA-2cq5-mf3v-mx44 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-2cq5-mf3v-mx44 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-2cq5-mf3v-mx44?

O3 pinpoints whether GHSA-2cq5-mf3v-mx44 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-2cq5-mf3v-mx44 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2cq5-mf3v-mx44 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-2cq5-mf3v-mx44 published, and has it been updated?

GHSA-2cq5-mf3v-mx44 was published on April 17, 2026 and was last updated on May 8, 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-2cq5-mf3v-mx44

HIGH

GHSA-2cq5-mf3v-mx44 is a high-severity (CVSS 8.8) vulnerability in openclaw. O3 Security confirms whether GHSA-2cq5-mf3v-mx44 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: busybox and toybox applet execution weakened exec approval binding

Also known asCVE-2026-43530

Published

Apr 17, 2026

Updated

May 8, 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.1Mdownloads / week

Description

Summary

busybox and toybox applet execution weakened exec approval binding.

Affected Packages / Versions

Package: openclaw
Ecosystem: npm
Affected versions: >= 2026.2.23 < 2026.4.12
Patched versions: >= 2026.4.12

Impact

Opaque multi-call binaries such as busybox and toybox could obscure which applet or script-like behavior would actually run, weakening exec approval binding and risk classification.

Technical Details

The fix treats busybox and toybox as opaque mutable script runners and fails closed rather than binding unsafe applet invocations.

Fix

The issue was fixed in #65713. The first stable tag containing the fix is v2026.4.12, and [email protected] includes the fix.

Fix Commit(s)

666f48d9b882a8a1415ca53f9567c72499d850c9
PR: #65713

Release Process Note

Users should upgrade to openclaw 2026.4.12 or newer. The latest npm release, 2026.4.14, already includes the fix.

Credits

Thanks to @decsecre583 for reporting this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.2.23&&< 2026.4.12	2026.4.12

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

Frequently Asked Questions

## Summary busybox and toybox applet execution weakened exec approval binding. ## Affected Packages / Versions - Package: `openclaw` - Ecosystem: npm - Affected versions: `>= 2026.2.23 < 2026.4.12` - Patched versions: `>= 2026.4.12` ## Impact Opaque multi-call binaries such as `busybox` and `toybox` could obscure which applet or script-like behavior would actually run, weakening exec approval binding and risk classification. ## Technical Details The fix treats `busybox` and `toybox` as opaque mutable script runners and fails closed rather than binding unsafe applet invocations. ## Fix

O3 Security · Impact-Aware SCA

Is GHSA-2cq5-mf3v-mx44 in your dependencies?

O3 detects GHSA-2cq5-mf3v-mx44 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