How severe is GHSA-7xmq-g46g-f8pv?

No CVSS score has been assigned to GHSA-7xmq-g46g-f8pv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7xmq-g46g-f8pv?

GHSA-7xmq-g46g-f8pv affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-7xmq-g46g-f8pv?

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

How do I detect GHSA-7xmq-g46g-f8pv 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-7xmq-g46g-f8pv 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-7xmq-g46g-f8pv actively exploited in the wild?

No public exploit code has been indexed for GHSA-7xmq-g46g-f8pv 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-7xmq-g46g-f8pv published, and has it been updated?

GHSA-7xmq-g46g-f8pv was published on March 2, 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: Sandbox media TOCTOU could read files outside sandbox rootGHSA-7xmq-g46g-f8pv

GHSA-7xmq-g46g-f8pv is a security vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

Published

Mar 2, 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

Sandbox media handling had a time-of-check/time-of-use gap: media paths could be validated first and read later through a separate path. A symlink retarget between those steps could cause reads outside sandboxRoot.

Impact

Affected versions could permit host file reads outside the intended sandbox root in media attachment/image flows.

Fix

Media reads now use consolidated root-scoped, boundary-safe read paths at use time, removing check/use drift across call sites.

Affected and Patched Versions

Affected: <= 2026.2.26
Patched: 2026.3.1

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	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-7xmq-g46g-f8pv 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 Sandbox media handling had a time-of-check/time-of-use gap: media paths could be validated first and read later through a separate path. A symlink retarget between those steps could cause reads outside `sandboxRoot`. ### Impact Affected versions could permit host file reads outside the intended sandbox root in media attachment/image flows. ### Fix Media reads now use consolidated root-scoped, boundary-safe read paths at use time, removing check/use drift across call sites. ### Affected and Patched Versions - Affected: `<= 2026.2.26` - Patched: `2026.3.1`

O3 Security · Impact-Aware SCA

Is GHSA-7xmq-g46g-f8pv in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works