OpenClaw Vulnerability: Time-of-Check/Time-of-Use Race Condition in OpenShell FS Bridge
Summary
GHSA-6f72-9gxx-98mj: Duplicate Advisory: OpenClaw: OpenShell FS bridge writes stay pinned to the sandbox mount root. Affects openclaw versions < 2026.4.22. Fixed in 2026.4.22. 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 filesystem operations within applications. It allows developers to create secure environments for file operations, ensuring that files are written only within designated mount points. However, a vulnerability has been identified in versions prior to 2026.4.22, which exposes the package to potential security risks due to improper handling of filesystem writes.
Vulnerability Detail
The vulnerability arises from a time-of-check/time-of-use race condition in OpenShell's sandbox filesystem writes. This flaw allows attackers to exploit symlink swaps during filesystem operations, enabling them to redirect writes outside the intended mount root. As a result, malicious actors can bypass sandbox restrictions, potentially leading to unauthorized file access or modification. The severity of this vulnerability is classified as moderate, with a CVSS score of 5.3, indicating a significant risk to applications utilizing OpenClaw.
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.4.22
This is the first release that contains the fix.
npm install openclaw@2026.4.22Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
If immediate upgrading is not feasible, consider implementing strict access controls on filesystem operations to limit the potential impact of this vulnerability. Additionally, avoid using symlinks in sensitive filesystem operations until the package is updated.
Conclusion
The OpenClaw vulnerability presents a significant risk due to a time-of-check/time-of-use race condition in its sandbox filesystem operations. It is crucial for developers using this package to update to the latest version to mitigate potential security threats. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.
See every vulnerability recorded for openclaw →
FAQ
The vulnerability is a time-of-check/time-of-use race condition that allows attackers to redirect filesystem writes outside the intended mount root.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If exploited, attackers can bypass sandbox restrictions, leading to unauthorized file access or modification, which could compromise application security.
Yes, the vulnerability has been patched in version 2026.4.22 of OpenClaw. It is recommended to update to this version or later.
Implement strict access controls on filesystem operations and avoid using symlinks in sensitive operations until you can upgrade.
References
Related vulnerabilities
Recent vulnerabilities recorded for openclaw.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.