How severe is GHSA-w6wx-jq6j-6mcj?

No CVSS score has been assigned to GHSA-w6wx-jq6j-6mcj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w6wx-jq6j-6mcj?

GHSA-w6wx-jq6j-6mcj affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-w6wx-jq6j-6mcj?

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

How do I detect GHSA-w6wx-jq6j-6mcj in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-w6wx-jq6j-6mcj 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-w6wx-jq6j-6mcj?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w6wx-jq6j-6mcj can be triaged on real exposure rather than presence alone.

Is GHSA-w6wx-jq6j-6mcj actively exploited in the wild?

No public exploit code has been indexed for GHSA-w6wx-jq6j-6mcj 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-w6wx-jq6j-6mcj?

GHSA-w6wx-jq6j-6mcj has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 1th 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.

What type of vulnerability is GHSA-w6wx-jq6j-6mcj?

GHSA-w6wx-jq6j-6mcj is classified as CWE-367 (CWE-367). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w6wx-jq6j-6mcj published, and has it been updated?

GHSA-w6wx-jq6j-6mcj was published on April 7, 2026 and was last updated on July 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

Not in CISA KEV

GHSA-w6wx-jq6j-6mcj — openclaw

Fix: openclaw/openclaw@176c059

GHSA-w6wx-jq6j-6mcj is a CWE-367 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw: pnpm dlx approvals did not bind local script operands

Also known asCVE-2026-41360

Published

Apr 7, 2026

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs1th percentile — riskier than 1% of all scored CVEsHighest risk

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.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

3.1Mdownloads / week

Description

Summary

Before OpenClaw 2026.4.2, pnpm dlx approval planning did not bind local script operands the same way as related pnpm exec flows. A local script approved through a pnpm dlx path could be replaced before execution without invalidating the approval.

Impact

An operator could approve a benign local script and then execute modified script contents through the still-valid approval plan. This was an approval-integrity bug in the node-host command-planning path.

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.4.1
Patched versions: >= 2026.4.2
Latest published npm version: 2026.4.1

Fix Commit(s)

176c059b05357df1bc09d4328a2380670859eeff — bind local scripts in pnpm dlx approval plans

Release Process Note

The fix is present on main and is staged for OpenClaw 2026.4.2. Publish this advisory after the 2026.4.2 npm release is live.

Thanks @Kazamayc for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.4.2`npm install openclaw@2026.4.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w6wx-jq6j-6mcj 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w6wx-jq6j-6mcj can be triaged on real exposure rather than presence alone.

Tailored to GHSA-w6wx-jq6j-6mcj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Before OpenClaw 2026.4.2, `pnpm dlx` approval planning did not bind local script operands the same way as related `pnpm exec` flows. A local script approved through a `pnpm dlx` path could be replaced before execution without invalidating the approval. ## Impact An operator could approve a benign local script and then execute modified script contents through the still-valid approval plan. This was an approval-integrity bug in the node-host command-planning path. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `<= 2026.4.1` - Patched versions: `>

O3 Security · Impact-Aware SCA

Is GHSA-w6wx-jq6j-6mcj in your dependencies?

O3 Security finds GHSA-w6wx-jq6j-6mcj across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works