How severe is GHSA-9f72-qcpw-2hxc?

No CVSS score has been assigned to GHSA-9f72-qcpw-2hxc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9f72-qcpw-2hxc?

GHSA-9f72-qcpw-2hxc affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-9f72-qcpw-2hxc?

Update openclaw to 2026.2.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9f72-qcpw-2hxc is resolved across your whole dependency graph.

How do I detect GHSA-9f72-qcpw-2hxc in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-9f72-qcpw-2hxc 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-9f72-qcpw-2hxc?

O3 pinpoints whether GHSA-9f72-qcpw-2hxc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-9f72-qcpw-2hxc actively exploited in the wild?

No public exploit code has been indexed for GHSA-9f72-qcpw-2hxc 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-9f72-qcpw-2hxc published, and has it been updated?

GHSA-9f72-qcpw-2hxc 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

GHSA-9f72-qcpw-2hxc

OpenClaw: Native prompt image auto-load did not honor tools.fs.workspaceOnly in sandboxed runs

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

4.3Mdownloads / week

Description

Summary

In sandboxed runs, native prompt image auto-load did not honor tools.fs.workspaceOnly=true.

This optional hardening setting is not enabled by default. When operators enabled it, prompt text could still reference mounted out-of-workspace image paths (for example /agent/secret.png) and load those image bytes for vision-capable model input.

Affected Packages / Versions

Package: openclaw (npm)
Latest published npm version at triage time: 2026.2.23
Vulnerable version range: <= 2026.2.23
Patched version (planned next release): 2026.2.24

Conditions Required

This issue required all of the following:

sandbox mode enabled,
tools.fs.workspaceOnly=true configured,
an out-of-workspace mount path reachable from the sandbox (for example /agent),
vision-capable model path active for native prompt image loading.

Technical Details

Native prompt image ingestion (detectAndLoadPromptImages / loadImageFromRef) resolved and read sandbox paths but did not apply the same workspace-root assertion used by file tools when tools.fs.workspaceOnly was set.

Fix Commit(s)

370d115549c0dadace0902775eea0d5094aedfdc

Verification

pnpm check
pnpm exec vitest run --config vitest.gateway.config.ts
pnpm test:fast

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.24) so once npm release is available, this advisory only needs publish action.

OpenClaw thanks @tdjackey for reporting.

Publication Update (2026-02-25)

[email protected] is published on npm and contains the fix commit(s) listed above. This advisory now marks >= 2026.2.24 as patched.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.24

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.2.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9f72-qcpw-2hxc 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 pinpoints whether GHSA-9f72-qcpw-2hxc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-9f72-qcpw-2hxc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary In sandboxed runs, native prompt image auto-load did not honor `tools.fs.workspaceOnly=true`. This optional hardening setting is **not enabled by default**. When operators enabled it, prompt text could still reference mounted out-of-workspace image paths (for example `/agent/secret.png`) and load those image bytes for vision-capable model input. ### Affected Packages / Versions - Package: `openclaw` (npm) - Latest published npm version at triage time: `2026.2.23` - Vulnerable version range: `<= 2026.2.23` - Patched version (planned next release): `2026.2.24` ### Conditions Requi

O3 Security · Impact-Aware SCA

Is GHSA-9f72-qcpw-2hxc in your dependencies?

O3 detects GHSA-9f72-qcpw-2hxc across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works