OpenClaw Sandbox Escape via Symlink Traversal
The openclaw npm package versions up to 2026.3.28 are vulnerable to a sandbox escape due to unrestricted file synchronization and symlink traversal, allowing attackers to potentially access or modify files outside the intended sandbox.
Triage facts
Revision 2- Evidence
- Unknown
- Severity
- High
- Sources
- 1 public source
- Freshness
- Revision 2Apr 3, 02:49 UTC
- Detection
- 2 rules
Revision history 1 entry · Revision 2
- Revision 2
Repaired a legacy canonical identity collision
Changed: slug
The openclaw npm package, a tool used for file synchronization and mirroring, contained a critical vulnerability affecting versions up to 2026.3.28. This flaw allowed for a sandbox escape through unrestricted file synchronization combined with symlink traversal. Specifically, the "mirror-boundary" could be bypassed, enabling malicious actors to read or write files outside the designated confines of the sandbox. The vulnerability was reported by AntAISecurityLab and addressed in version 2026.3.31, with initial mitigation efforts focusing on excluding hooks, followed by a comprehensive hardening against symlink-based attacks in subsequent updates. This vulnerability allows attackers to potentially escalate privileges and compromise the integrity of the system where OpenClaw is used.
Attack Chain
- Attacker gains control over a file within the sandboxed environment.
- Attacker creates a symbolic link within the controlled file, pointing to a target file or directory outside the sandbox (e.g.,
/etc/passwd, user's home directory). - OpenClaw's mirroring functionality initiates a synchronization process.
- Due to insufficient boundary checks, OpenClaw follows the symbolic link during file synchronization.
- OpenClaw reads the content of the target file outside the sandbox via the symlink.
- The attacker receives the data outside of the intended sandbox.
- Alternatively, if OpenClaw attempts to write to the symlinked file, it modifies files outside of the intended sandbox.
- Successful exploitation leads to arbitrary file read/write, potentially escalating privileges or compromising sensitive data.
Impact
Successful exploitation of this vulnerability allows attackers to bypass the intended security restrictions of the openclaw sandbox. The primary impact is arbitrary file read and write access outside of the sandbox, potentially leading to privilege escalation, sensitive data disclosure, or system compromise. While the specific number of affected installations is unknown, any system using vulnerable versions of openclaw for file synchronization is at risk. The successful exploitation allows attackers to perform actions they should not be authorized to do based on the sandbox restrictions.
Recommendation
- Upgrade the
openclawnpm package to version 2026.3.31 or later to address the vulnerability (reference: Affected Packages / Versions). - Monitor file system events for the creation of suspicious symbolic links within the openclaw working directory that point outside the intended sandbox using a suitable host-based intrusion detection system (HIDS).
- Implement stricter file access controls and boundary checks in applications utilizing file synchronization to prevent symlink traversal attacks.
Detection coverage 2
Detect Symbolic Link Creation in OpenClaw Directories
mediumDetects the creation of symbolic links within directories typically used by OpenClaw, which could indicate an attempt to exploit the symlink traversal vulnerability.
Detect Access to Sensitive Files via OpenClaw Process
highDetects OpenClaw processes accessing sensitive files outside of its normal operating scope, potentially indicating exploitation of the symlink traversal vulnerability.
Detection queries are available on the platform. Get full rules →