Sandbox escape via dangling symlink leaf
Published Aug 6, 2026 · Updated Aug 6, 2026
Link following in OpenClaw-CN openclaw-cn 0.2.0 and 0.2.1 allows remote authenticated users to write files outside the workspace. assertNoSymlinkEscape returns success when lstat encounters ENOENT at a dangling symlink leaf, after which applyPatch passes the unresolved path to fs.writeFile. Exploitation requires enabled apply_patch access, an allowed model, workspace write access, and a prepared dangling symlink; resulting writes remain limited to the gateway process permissions.
Summary
What happened
Link following in OpenClaw-CN openclaw-cn 0.2.0 and 0.2.1 allows remote authenticated users to write files outside the workspace. assertNoSymlinkEscape returns success when lstat encounters ENOENT at a dangling symlink leaf, after which applyPatch passes the unresolved path to fs.writeFile. Exploitation requires enabled apply_patch access, an allowed model, workspace write access, and a prepared dangling symlink; resulting writes remain limited to the gateway process permissions.
The record
- CVE
- CVE-2026-19008
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- OpenClaw-CN
- Product
- openclaw-cn
- Classifications
- CWE-59, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.2.0
- Affected versionversion=0.2.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Dangling symlink apply_patch verification PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo