Sandbox boundary bypass via raced temporary file creation
Published Mar 31, 2026 · Updated Mar 31, 2026
Sandbox boundary bypass in OpenClaw before 2026.3.11 allows local users to write data outside a validated sandbox path. The fs-bridge staging flow creates and populates a temporary file through target-directory shell paths before the final destination check, so a raced parent-path alias redirects that materialization. Exploitation requires low-privileged local access and precise race timing, and its consequence is bounded to integrity and availability within writable mount scope.
Summary
What happened
Sandbox boundary bypass in OpenClaw before 2026.3.11 allows local users to write data outside a validated sandbox path. The fs-bridge staging flow creates and populates a temporary file through target-directory shell paths before the final destination check, so a raced parent-path alias redirects that materialization. Exploitation requires low-privileged local access and precise race timing, and its consequence is bounded to integrity and availability within writable mount scope.
The record
- CVE
- CVE-2026-32988
- Published
- Mar 31, 2026
- Updated
- Mar 31, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-59, CWE-367, T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 31, 2026CVE publishedPublication date reported by the CVE source.
- Mar 31, 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 <2026.3.11
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
No public exploit references are available in this record.
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