How severe is GHSA-mwcg-wfq3-4gjc?

No CVSS score has been assigned to GHSA-mwcg-wfq3-4gjc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mwcg-wfq3-4gjc?

GHSA-mwcg-wfq3-4gjc affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-mwcg-wfq3-4gjc?

Update openclaw to 2026.2.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mwcg-wfq3-4gjc is resolved across your whole dependency graph.

How do I detect GHSA-mwcg-wfq3-4gjc 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-mwcg-wfq3-4gjc 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-mwcg-wfq3-4gjc?

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

Is GHSA-mwcg-wfq3-4gjc actively exploited in the wild?

No public exploit code has been indexed for GHSA-mwcg-wfq3-4gjc 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-mwcg-wfq3-4gjc?

GHSA-mwcg-wfq3-4gjc has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 2th 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-mwcg-wfq3-4gjc?

GHSA-mwcg-wfq3-4gjc 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-mwcg-wfq3-4gjc published, and has it been updated?

GHSA-mwcg-wfq3-4gjc 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

Not in CISA KEV

GHSA-mwcg-wfq3-4gjc — openclaw

Fix: openclaw/openclaw@f789f88

GHSA-mwcg-wfq3-4gjc is a CWE-367 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw's system.run approval TOCTOU via mutable symlink cwd target on node host

Also known asCVE-2026-32043

Published

Mar 3, 2026

Updated

Mar 30, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-mwcg-wfq3-4gjc.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs2th percentile — riskier than 2% 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.3Mdownloads / week

Description

Summary

In [email protected], approval-bound system.run on node hosts could be influenced by mutable symlink cwd targets between approval and execution.

Details

Approval matching on the gateway validated command/argv and binding fields, including cwd, as provided text. Node execution later used runtime cwd resolution. A symlinked cwd could therefore be retargeted after approval and before spawn.

OpenClaw's trust model does not treat one shared gateway as a multi-tenant adversarial boundary, but approval integrity is still a security boundary for operator-reviewed command execution.

Affected Packages / Versions

Package: openclaw (npm)
Affected: <= 2026.2.24
Patched: >= 2026.2.25

Fix Commit(s)

f789f880c934caa8be25b38832f27f90f37903db

Remediation

The fix adds defense-in-depth hardening for approval-bound node execution:

reject symlink cwd paths for approval-bound system.run
canonicalize path-like executable argv before spawn
bind CLI approval requests to exact commandArgv

Release Process Note

Patched version is pre-set to the release (2026.2.25). Advisory published with npm release 2026.2.25.

OpenClaw thanks @tdjackey for reporting.

Affected Packages

1 total 1 fixed

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

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.2.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mwcg-wfq3-4gjc 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-mwcg-wfq3-4gjc can be triaged on real exposure rather than presence alone.

Tailored to GHSA-mwcg-wfq3-4gjc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary In `[email protected]`, approval-bound `system.run` on node hosts could be influenced by mutable symlink `cwd` targets between approval and execution. ### Details Approval matching on the gateway validated command/argv and binding fields, including `cwd`, as provided text. Node execution later used runtime `cwd` resolution. A symlinked `cwd` could therefore be retargeted after approval and before spawn. OpenClaw's trust model does not treat one shared gateway as a multi-tenant adversarial boundary, but approval integrity is still a security boundary for operator-reviewed command

O3 Security · Impact-Aware SCA

Is GHSA-mwcg-wfq3-4gjc in your dependencies?

O3 Security finds GHSA-mwcg-wfq3-4gjc 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