How severe is GHSA-w9j9-w4cp-6wgr?

No CVSS score has been assigned to GHSA-w9j9-w4cp-6wgr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w9j9-w4cp-6wgr?

GHSA-w9j9-w4cp-6wgr affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-w9j9-w4cp-6wgr?

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

How do I detect GHSA-w9j9-w4cp-6wgr 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-w9j9-w4cp-6wgr 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-w9j9-w4cp-6wgr?

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

Is GHSA-w9j9-w4cp-6wgr actively exploited in the wild?

No public exploit code has been indexed for GHSA-w9j9-w4cp-6wgr 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-w9j9-w4cp-6wgr published, and has it been updated?

GHSA-w9j9-w4cp-6wgr was published on April 9, 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-w9j9-w4cp-6wgr — openclaw

GHSA-w9j9-w4cp-6wgr is a security vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw Host-Exec Environment Variable Injection

Published

Apr 9, 2026

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

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

Impact

OpenClaw Host-Exec Environment Variable Injection.

Host exec could inherit environment variables that influence interpreters, shells, or build tools.

OpenClaw is a user-controlled local assistant. This advisory is scoped to the OpenClaw trust model and does not assume a multi-tenant service boundary.

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.3.28
Patched versions: 2026.4.8

Fix

The issue was fixed on main and is available in the patched npm version listed above. The verified fixed tree is commit d7c3210cd6f5fdfdc1beff4c9541673e814354d5.

Verification

The fix was re-checked against main before publication, including targeted regression tests for the affected security boundary.

Credits

Thanks @wsparks-vc for reporting.

Affected Packages

1 total 1 fixed

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

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

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

Frequently Asked Questions

## Impact OpenClaw Host-Exec Environment Variable Injection. Host exec could inherit environment variables that influence interpreters, shells, or build tools. OpenClaw is a user-controlled local assistant. This advisory is scoped to the OpenClaw trust model and does not assume a multi-tenant service boundary. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `<= 2026.3.28` - Patched versions: `2026.4.8` ## Fix The issue was fixed on `main` and is available in the patched npm version listed above. The verified fixed tree is commit `d7c3210cd6f5fdfdc1beff4c

O3 Security · Impact-Aware SCA

Is GHSA-w9j9-w4cp-6wgr in your dependencies?

O3 Security finds GHSA-w9j9-w4cp-6wgr 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