GHSA-64qx-vpxx-mvqf
HIGHGHSA-64qx-vpxx-mvqf is a high-severity (CVSS 7.1) CWE-73 vulnerability in openclaw. O3 Security confirms whether GHSA-64qx-vpxx-mvqf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenClaw has an arbitrary transcript path file write via gateway sessionFile
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
openclawnpmDescription
Summary
In OpenClaw versions prior to 2026.2.12, the gateway accepted an untrusted sessionFile path when resolving the session transcript file. This could allow an authenticated gateway client to create and append OpenClaw session transcript records at an arbitrary path on the gateway host.
Affected Versions
- Affected: openclaw
< 2026.2.12 - Patched: openclaw
>= 2026.2.12(recommended:>= 2026.2.13)
Impact
An authenticated gateway client could influence where the gateway writes transcript data by supplying sessionFile outside of the sessions directory. Depending on deployment and filesystem permissions, this may enable arbitrary file creation and repeated appends, leading to configuration corruption and/or denial of service.
This issue does not, by itself, provide a proven remote code execution path.
Fix
The transcript path is now constrained to the sessions directory via resolveSessionFilePath(...) containment checks.
Fix commits:
- 4199f9889f0c307b77096a229b9e085b8d856c26
- (compat) 25950bcbb8ba4d8cde002557f6e27c219ae4deda
Credits
Thanks to @tubadeligoz for the report.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.2.12 |
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.2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-64qx-vpxx-mvqf 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-64qx-vpxx-mvqf 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-64qx-vpxx-mvqf. 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-64qx-vpxx-mvqf in your dependencies?
O3 detects GHSA-64qx-vpxx-mvqf across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.