How severe is GHSA-6f6j-wx9w-ff4j?

No CVSS score has been assigned to GHSA-6f6j-wx9w-ff4j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6f6j-wx9w-ff4j?

GHSA-6f6j-wx9w-ff4j affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-6f6j-wx9w-ff4j?

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

How do I detect GHSA-6f6j-wx9w-ff4j 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-6f6j-wx9w-ff4j 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-6f6j-wx9w-ff4j?

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

Is GHSA-6f6j-wx9w-ff4j actively exploited in the wild?

No public exploit code has been indexed for GHSA-6f6j-wx9w-ff4j 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-6f6j-wx9w-ff4j?

GHSA-6f6j-wx9w-ff4j has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 28th 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.

When was GHSA-6f6j-wx9w-ff4j published, and has it been updated?

GHSA-6f6j-wx9w-ff4j was published on March 2, 2026 and was last updated on March 20, 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-6f6j-wx9w-ff4j — openclaw

GHSA-6f6j-wx9w-ff4j is a security vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

CpenClaw's ACPX Windows wrapper shell fallback allowed cwd injection in specific paths

Also known asCVE-2026-31999

Published

Mar 2, 2026

Updated

Mar 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, 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-6f6j-wx9w-ff4j.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

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

2.5Mdownloads / week

Description

Summary

On Windows ACPX paths, wrapper resolution for .cmd/.bat could fall back to shell execution in ways that allowed cwd influence to alter execution behavior.

Impact

In affected Windows ACPX configurations, this could enable command execution integrity loss through cwd-influenced wrapper resolution.

Fix

Wrapper resolution now prefers explicit PATH/PATHEXT entrypoint resolution and unwrapped Node/EXE execution, with strict fail-closed handling enabled by default for unresolvable wrapper cases.

Affected and Patched Versions

Affected: >= 2026.2.26, < 2026.3.1
Patched: 2026.3.1

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.2.26&&< 2026.3.1	2026.3.1`npm install openclaw@2026.3.1`

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

Tailored to GHSA-6f6j-wx9w-ff4j. 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 ACPX paths, wrapper resolution for `.cmd`/`.bat` could fall back to shell execution in ways that allowed `cwd` influence to alter execution behavior. ### Impact In affected Windows ACPX configurations, this could enable command execution integrity loss through cwd-influenced wrapper resolution. ### Fix Wrapper resolution now prefers explicit PATH/PATHEXT entrypoint resolution and unwrapped Node/EXE execution, with strict fail-closed handling enabled by default for unresolvable wrapper cases. ### Affected and Patched Versions - Affected: `>= 2026.2.26, < 2026.3.1` - Pa

O3 Security · Impact-Aware SCA

Is GHSA-6f6j-wx9w-ff4j in your dependencies?

O3 Security finds GHSA-6f6j-wx9w-ff4j 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