Sandbox Boundary Bypass in OpenClaw: Vulnerability in File Write Operations

openclaw Updated 13 Mar 2026

Summary

13/03/2026
MODERATE
Yes i
Moderate
6.3

GHSA-xvx8-77m6-gwg6: OpenClaw: Sandbox writeFile commit could race outside the validated path. Affects openclaw versions < 2026.3.11. Fixed in 2026.3.11. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

OpenClaw is an npm package designed to facilitate sandboxed file operations within containerized environments. It allows developers to perform file write operations securely, ensuring that files are written only within validated paths. However, a recent vulnerability has been identified that could allow malicious actors to exploit the system and write files outside of the intended sandbox boundaries.

Vulnerability Detail

The vulnerability arises from the sandbox fs-bridge's writeFile commit step, which utilized an unanchored container path during the final move operation. This flaw creates a time-of-check-time-of-use race condition, enabling an attacker to manipulate parent-path changes within the sandbox. As a result, legitimate writeFile operations could be redirected to locations outside the validated writable path, leading to potential data breaches or unauthorized file access.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading 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.11

Tip — 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 and monitoring file operations within your sandbox environment to mitigate potential exploitation until the package can be updated.

Conclusion

The OpenClaw package has a vulnerability that allows for sandbox boundary bypass during file write operations. Users are strongly advised to upgrade to version 2026.3.11 or later to mitigate this risk. Implementing workarounds and monitoring can provide temporary relief until the upgrade is completed.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The vulnerability allows for a sandbox boundary bypass, enabling files to be written outside of the validated paths due to a race condition in the writeFile commit process.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

The CVSS score of this vulnerability is 6.3, indicating a moderate severity level.

If you cannot upgrade immediately, implement strict access controls and monitor file operations within your sandbox environment to reduce the risk of exploitation.

More information about OpenClaw can be found on its official npm page or GitHub repository, where you can also track updates and fixes.

Related vulnerabilities

Recent vulnerabilities recorded for openclaw.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading 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.11

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback