How severe is GHSA-j6c7-3h5x-99g9?

No CVSS score has been assigned to GHSA-j6c7-3h5x-99g9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j6c7-3h5x-99g9?

GHSA-j6c7-3h5x-99g9 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-j6c7-3h5x-99g9?

Update openclaw to 2026.4.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j6c7-3h5x-99g9 is resolved across your whole dependency graph.

How do I detect GHSA-j6c7-3h5x-99g9 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-j6c7-3h5x-99g9 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-j6c7-3h5x-99g9?

O3 pinpoints whether GHSA-j6c7-3h5x-99g9 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-j6c7-3h5x-99g9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-j6c7-3h5x-99g9 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-j6c7-3h5x-99g9?

GHSA-j6c7-3h5x-99g9 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 34th 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-j6c7-3h5x-99g9?

GHSA-j6c7-3h5x-99g9 is classified as CWE-184 (CWE-184). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j6c7-3h5x-99g9 published, and has it been updated?

GHSA-j6c7-3h5x-99g9 was published on April 17, 2026 and was last updated on May 5, 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-j6c7-3h5x-99g9

Fix: openclaw/openclaw#65717

GHSA-j6c7-3h5x-99g9 is a CWE-184 vulnerability in openclaw. O3 Security confirms whether GHSA-j6c7-3h5x-99g9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: Shell-wrapper detection missed env-argv assignment injection forms

Also known asCVE-2026-42435

Published

Apr 17, 2026

Updated

May 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-j6c7-3h5x-99g9.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs34th percentile — riskier than 34% 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.

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

openclawnpm

2.7Mdownloads / week

Description

Summary

Shell-wrapper detection missed env-argv assignment injection forms.

Affected Packages / Versions

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

Impact

Exec preflight handling missed shell-wrapper and argv-level environment assignment forms that could affect execution semantics, including high-risk shell environment controls.

Technical Details

The fix broadens shell-wrapper detection and blocks environment assignments in argv forms. High-risk shell variables such as SHELLOPTS and PS4 are covered by the host environment security policy.

Fix

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

Fix Commit(s)

8f8492d172f4c5b4fd7dd9a47855ed620c8770ab
PR: #65717

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.22&&< 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-j6c7-3h5x-99g9 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-j6c7-3h5x-99g9 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-j6c7-3h5x-99g9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Shell-wrapper detection missed env-argv assignment injection forms. ## Affected Packages / Versions - Package: `openclaw` - Ecosystem: npm - Affected versions: `>= 2026.2.22 < 2026.4.12` - Patched versions: `>= 2026.4.12` ## Impact Exec preflight handling missed shell-wrapper and argv-level environment assignment forms that could affect execution semantics, including high-risk shell environment controls. ## Technical Details The fix broadens shell-wrapper detection and blocks environment assignments in argv forms. High-risk shell variables such as `SHELLOPTS` and `PS4` are co

O3 Security · Impact-Aware SCA

Is GHSA-j6c7-3h5x-99g9 in your dependencies?

O3 detects GHSA-j6c7-3h5x-99g9 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