GHSA-v8wv-jg3q-qwpq is a medium-severity (CVSS 6.2) Path Traversal vulnerability in openclaw. O3 Security confirms whether GHSA-v8wv-jg3q-qwpq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenClaw's message tool media parameter bypasses tool policy filesystem isolation
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
openclawnpmDescription
Summary
The message tool accepted mediaUrl and fileUrl aliases without applying the same sandbox localRoots validation as the canonical media path handling.
Impact
A caller constrained to sandbox media roots could read arbitrary local files by routing them through the alias parameters.
Affected Component
src/infra/outbound/message-action-params.ts, src/infra/outbound/message-action-runner.ts
Fixed Versions
- Affected:
< 2026.3.24 - Patched:
>= 2026.3.24 - Latest stable
2026.3.28contains the fix.
Fix
Fixed by commit 1d7cb6fc03 (fix: close sandbox media root bypass for mediaUrl/fileUrl aliases).
OpenClaw thanks @AntAISecurityLab for reporting.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.3.24 |
Detection & mitigation playbook
Open-source dependencyDetect
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.3.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v8wv-jg3q-qwpq 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-v8wv-jg3q-qwpq 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-v8wv-jg3q-qwpq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-v8wv-jg3q-qwpq in your dependencies?
O3 detects GHSA-v8wv-jg3q-qwpq across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.