How severe is GHSA-w9cg-v44m-4qv8?

No CVSS score has been assigned to GHSA-w9cg-v44m-4qv8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w9cg-v44m-4qv8?

GHSA-w9cg-v44m-4qv8 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-w9cg-v44m-4qv8?

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

How do I detect GHSA-w9cg-v44m-4qv8 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-w9cg-v44m-4qv8 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.

Is GHSA-w9cg-v44m-4qv8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-w9cg-v44m-4qv8 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-w9cg-v44m-4qv8 published, and has it been updated?

GHSA-w9cg-v44m-4qv8 was published on March 3, 2026 and was last updated on March 4, 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

OpenClaw affected by BASH_ENV / ENV startup-file injection into spawned shell commandsGHSA-w9cg-v44m-4qv8

Fix: openclaw/openclaw@2cdbade

GHSA-w9cg-v44m-4qv8 is a security vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 4, 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

2.4Mdownloads / week

Description

Summary

BASH_ENV / ENV startup-file injection could lead to unintended pre-command shell execution when attacker-controlled environment values were admitted and then inherited by host command execution paths.

Affected Packages / Versions

Package: openclaw (npm)
Affected: <= 2026.2.19-2
Fixed on main: 2cdbadee1f8fcaa93302d7debbfc529e19868ea4
Planned patched release version: 2026.2.21

Details

The fix hardens environment handling across all relevant execution paths:

Blocks dangerous startup/runtime env keys and prefixes in shared host env sanitization.
Sanitizes inherited ambient environment even when no per-request overrides are provided.
Blocks dangerous config-driven env injection before values enter process environment.
Uses the same sanitizer in macOS host execution paths.
Aligns skill env override sanitization with the shared dangerous-env policy.

Impact

Medium. Exploitation requires local/privileged influence over configuration or environment inputs; there is no standalone remote unauthenticated trigger from this issue alone.

Fix Commit(s)

2cdbadee1f8fcaa93302d7debbfc529e19868ea4

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.21). Once npm [email protected] is published, the advisory can be published without further field edits.

OpenClaw thanks @tdjackey for reporting.

Affected Packages

1 total 1 fixed

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

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.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w9cg-v44m-4qv8 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.

Frequently Asked Questions

### Summary `BASH_ENV` / `ENV` startup-file injection could lead to unintended pre-command shell execution when attacker-controlled environment values were admitted and then inherited by host command execution paths. ### Affected Packages / Versions - Package: `openclaw` (npm) - Affected: `<= 2026.2.19-2` - Fixed on `main`: `2cdbadee1f8fcaa93302d7debbfc529e19868ea4` - Planned patched release version: `2026.2.21` ### Details The fix hardens environment handling across all relevant execution paths: - Blocks dangerous startup/runtime env keys and prefixes in shared host env sanitization. - Sani

O3 Security · Impact-Aware SCA

Is GHSA-w9cg-v44m-4qv8 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works