OpenClaw Sandbox Bypass Vulnerability: Integrity and Availability Risk
Summary
GHSA-mj4p-rc52-m843: OpenClaw: Sandbox staged writes could escape the verified parent directory before commit. Affects openclaw versions < 2026.3.11. Fixed in 2026.3.11. 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 npm package designed to facilitate sandboxed file system operations, allowing developers to create secure environments for file manipulation. It provides features that ensure files are written in a controlled manner, preventing unauthorized access or modifications. However, a recent vulnerability has been identified that compromises the integrity of this sandboxing mechanism, potentially allowing attackers to write data outside the intended directories.
Vulnerability Detail
The vulnerability arises from a flaw in the temporary file creation process within OpenClaw. In affected versions, the validation of the destination directory occurs only at the final commit stage, allowing a race condition where an attacker could change the parent path alias. This could lead to the creation of temporary files outside the verified writable mount, resulting in unauthorized data manipulation and integrity breaches. The vulnerability has a CVSS score of 7.5, indicating a high severity level.
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.3.11
This is the first release that contains the fix.
npm install openclaw@2026.3.11Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
If upgrading is not immediately feasible, users can implement a temporary workaround by manually validating the paths used for temporary file creation to ensure they remain within the intended writable mount. However, this is not a substitute for applying the official patch.
Conclusion
The OpenClaw vulnerability presents a significant risk to applications relying on its sandboxing features. Users are strongly encouraged to upgrade to version 2026.3.11 or later to mitigate this risk. Regular monitoring for vulnerabilities using tools like Vulert can help maintain application security.
See every vulnerability recorded for openclaw →
FAQ
The vulnerability allows for a sandbox boundary bypass, enabling potential unauthorized writes outside the intended directory.
You can use Vulert's playground at Vulert Scanner to monitor and check for vulnerabilities in your application without needing to sign up.
If exploited, the vulnerability could lead to data integrity issues and unauthorized access to sensitive files outside the intended sandbox.
Yes, the vulnerability poses a risk to data integrity and availability, potentially leading to data loss or corruption.
Implement manual path validation for temporary file creation as a temporary workaround until you can upgrade to the patched version.
References
Related vulnerabilities
Recent vulnerabilities recorded for openclaw.
