How severe is GHSA-fg3m-vhrr-8gj6?

No CVSS score has been assigned to GHSA-fg3m-vhrr-8gj6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fg3m-vhrr-8gj6?

GHSA-fg3m-vhrr-8gj6 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-fg3m-vhrr-8gj6?

Update openclaw to 2026.2.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fg3m-vhrr-8gj6 is resolved across your whole dependency graph.

How do I detect GHSA-fg3m-vhrr-8gj6 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-fg3m-vhrr-8gj6 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-fg3m-vhrr-8gj6?

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

Is GHSA-fg3m-vhrr-8gj6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-fg3m-vhrr-8gj6 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-fg3m-vhrr-8gj6?

GHSA-fg3m-vhrr-8gj6 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th 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-fg3m-vhrr-8gj6?

GHSA-fg3m-vhrr-8gj6 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-fg3m-vhrr-8gj6 published, and has it been updated?

GHSA-fg3m-vhrr-8gj6 was published on March 3, 2026 and was last updated on March 19, 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-fg3m-vhrr-8gj6 — openclaw

Fix: openclaw/openclaw@ba7be01

GHSA-fg3m-vhrr-8gj6 is a OS Command Injection vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw has Windows Lobster shell fallback command injection in constrained fallback path

Also known asCVE-2026-31995

Published

Mar 3, 2026

Updated

Mar 19, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 19, 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-fg3m-vhrr-8gj6.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% 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

On Windows, the Lobster extension previously retried certain spawn failures (ENOENT/EINVAL) with shell: true for wrapper compatibility. In that fallback path, tool-provided arguments could be interpreted by cmd.exe if fallback was triggered.

Affected Packages / Versions

Package: openclaw (npm)
Latest published version at triage: 2026.2.17
Affected range: >= 2026.1.21 <= 2026.2.17
Patched version: 2026.2.19 (pre-set for next release)

Fix

The Windows shell fallback was removed. Wrapper compatibility is preserved by resolving .cmd/.bat shims to a concrete Node entrypoint (or executable) and executing with explicit argv (no shell). If a safe entrypoint cannot be resolved, execution now fails closed with a guided error.

Fix Commit(s)

ba7be018da354ea9f803ed356d20464df0437916

Severity Context

This issue requires Windows plus fallback-triggering conditions, and argument control through a local operator-defined workflow.

OpenClaw thanks @tdjackey for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.1.21&&< 2026.2.19	2026.2.19`npm install openclaw@2026.2.19`

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

Tailored to GHSA-fg3m-vhrr-8gj6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary On Windows, the Lobster extension previously retried certain spawn failures (`ENOENT`/`EINVAL`) with `shell: true` for wrapper compatibility. In that fallback path, tool-provided arguments could be interpreted by `cmd.exe` if fallback was triggered. ### Affected Packages / Versions - Package: `openclaw` (npm) - Latest published version at triage: `2026.2.17` - Affected range: `>= 2026.1.21 <= 2026.2.17` - Patched version: `2026.2.19` (pre-set for next release) ### Fix The Windows shell fallback was removed. Wrapper compatibility is preserved by resolving `.cmd`/`.bat` shims to a

O3 Security · Impact-Aware SCA

Is GHSA-fg3m-vhrr-8gj6 in your dependencies?

O3 Security finds GHSA-fg3m-vhrr-8gj6 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