How severe is GHSA-cfvj-7rx7-fc7c?

No CVSS score has been assigned to GHSA-cfvj-7rx7-fc7c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cfvj-7rx7-fc7c?

GHSA-cfvj-7rx7-fc7c affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-cfvj-7rx7-fc7c?

Update openclaw to 2026.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cfvj-7rx7-fc7c is resolved across your whole dependency graph.

How do I detect GHSA-cfvj-7rx7-fc7c 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-cfvj-7rx7-fc7c 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-cfvj-7rx7-fc7c actively exploited in the wild?

No public exploit code has been indexed for GHSA-cfvj-7rx7-fc7c 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-cfvj-7rx7-fc7c?

GHSA-cfvj-7rx7-fc7c has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 4th 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-cfvj-7rx7-fc7c?

GHSA-cfvj-7rx7-fc7c is classified as CWE-59 (CWE-59). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cfvj-7rx7-fc7c published, and has it been updated?

GHSA-cfvj-7rx7-fc7c 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

OpenClaw: stageSandboxMedia destination symlink traversal can overwrite files outside sandbox workspaceGHSA-cfvj-7rx7-fc7c

Fix: openclaw/openclaw@17ede52

GHSA-cfvj-7rx7-fc7c is a CWE-59 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

Also known asCVE-2026-31990

Published

Mar 3, 2026

Updated

Mar 19, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 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-cfvj-7rx7-fc7c.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk+0.00%

Lower risk than most CVEs4th percentile — riskier than 4% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from 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.5Mdownloads / week

Description

Summary

stageSandboxMedia allowed destination symlink traversal during media staging, which could overwrite files outside the sandbox workspace root.

Impact

When sandbox media staging handled inbound files, destination writes under media/inbound were not destination-alias-safe. If a symlink existed in that destination path, the write could follow it and overwrite host files outside the intended sandbox workspace boundary.

Affected Packages / Versions

Package: openclaw (npm)
Latest published version checked: 2026.3.1
Affected: <= 2026.3.1
Patched versions: >= 2026.3.2 (released)

Root Cause

stageSandboxMedia validated source paths but wrote destination files with a direct copy path that did not enforce destination boundary/alias checks.

Remediation

The fix routes staging writes through root-scoped safe write primitives for both local and SCP-staged attachments, preventing destination symlink traversal escapes.

Fix Commit(s)

17ede52a4be3034f6ec4b883ac6b81ad0101558a

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

< 2026.3.2

range

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.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cfvj-7rx7-fc7c 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 `stageSandboxMedia` allowed destination symlink traversal during media staging, which could overwrite files outside the sandbox workspace root. ### Impact When sandbox media staging handled inbound files, destination writes under `media/inbound` were not destination-alias-safe. If a symlink existed in that destination path, the write could follow it and overwrite host files outside the intended sandbox workspace boundary. ### Affected Packages / Versions - Package: `openclaw` (npm) - Latest published version checked: `2026.3.1` - Affected: `<= 2026.3.1` - Patched versions: `>= 20

O3 Security · Impact-Aware SCA

Is GHSA-cfvj-7rx7-fc7c in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works