Arbitrary File Write Vulnerability in OpenClaw: Session Transcript Path Exposure
Summary
GHSA-64qx-vpxx-mvqf: OpenClaw has an arbitrary transcript path file write via gateway sessionFile. Affects openclaw versions < 2026.2.12. Fixed in 2026.2.12. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
OpenClaw is an open-source framework designed for building web applications with a focus on real-time communication and session management. It allows developers to create interactive applications by managing user sessions and facilitating data exchange. However, prior to version 2026.2.12, OpenClaw had a significant security flaw that allowed authenticated users to manipulate the session transcript file path, potentially leading to unauthorized file writes on the server.
Vulnerability Detail
The vulnerability arises from the gateway's acceptance of untrusted input for the 'sessionFile' path, which is used to resolve the session transcript file. This flaw allows authenticated clients to specify arbitrary paths outside the designated sessions directory, leading to potential file creation and data corruption. Although this vulnerability does not directly enable remote code execution, it poses risks such as configuration corruption and denial of service, depending on the server's filesystem permissions.
How To Fix
Latest published version: 2026.10.6 as of 22 Oct 2026
npm install openclaw@2026.10.6Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2026.2.12
This is the first release that contains the fix.
npm install openclaw@2026.2.12Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary measure, ensure that your server's filesystem permissions are configured to restrict write access to sensitive directories. Additionally, validate and sanitize any user input related to file paths to mitigate the risk of exploitation until the package is updated.
Conclusion
The arbitrary file write vulnerability in OpenClaw poses significant risks to applications using the framework. It is crucial for developers to update to the latest version to mitigate these risks and ensure the security of their applications. Implementing best practices for input validation and filesystem permissions can further enhance security until updates are applied.
See every vulnerability recorded for openclaw →
FAQ
The vulnerability has a CVSS score of 7.1, indicating a high level of severity.
No, this vulnerability does not directly provide a path for remote code execution, but it can lead to other serious issues like data corruption.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If an immediate update is not possible, implement strict input validation and adjust filesystem permissions to limit write access to sensitive directories.
The vulnerability was reported by a user identified as @tubadeligoz.
References
Related vulnerabilities
Recent vulnerabilities recorded for openclaw.
