OpenClaw Vulnerability: Path Handling Issue Leading to Potential Data Exfiltration
Summary
GHSA-33hm-cq8r-wc49: Temporary path handling could write outside OpenClaw temp boundary. Affects openclaw versions < 2026.2.24. Fixed in 2026.2.24. 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 package designed for managing sandboxed media inputs in applications. It provides a secure environment for processing media files, ensuring that only trusted paths are accessed. However, a recent vulnerability has been identified that allows absolute paths under the host's temporary directory to be accepted, potentially leading to unauthorized access to sensitive files outside the intended sandbox boundary.
Vulnerability Detail
The vulnerability arises from inadequate validation of local-path inputs in the OpenClaw sandbox environment. Specifically, the system accepts absolute paths that reside within the host's temporary directory without ensuring they remain within the designated sandbox root. This flaw can be exploited by attackers to read and exfiltrate files from the host's temporary directory, compromising the confidentiality of sensitive data. The issue is classified under CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) and CWE-284 (Improper Access Control), with a CVSS score of 6.1 indicating a moderate 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.2.24
This is the first release that contains the fix.
npm install openclaw@2026.2.24Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, users can manually validate and restrict the paths being used in their applications to ensure they do not point to sensitive files outside the sandbox. Implementing custom path validation logic can help mitigate the risk until the package is updated.
Conclusion
The OpenClaw vulnerability presents a significant risk due to improper path handling, allowing potential data exfiltration from the host's temporary directory. Users are strongly advised to update to the patched version and implement additional path validation measures to secure their applications.
See every vulnerability recorded for openclaw →
FAQ
The vulnerability allows absolute paths in the host's temporary directory to be accepted, which can lead to unauthorized access to files outside the sandbox.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without requiring any signup.
Implement custom path validation to restrict access to sensitive files and ensure that only trusted paths are used in your application.
The vulnerability can lead to high confidentiality risks, allowing attackers to read and exfiltrate sensitive files from the host's temporary directory.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing the package-lock.json file.
References
Related vulnerabilities
Recent vulnerabilities recorded for openclaw.
