openclaw
Affected
- introduced
0, fixed2026.3.11(semver)
Fixed versions
2026.3.11
Fix
- Fixed version
2026.3.11npm install [email protected]
Advisory
Also known as: CVE-2026-32977
OpenClaw: Sandbox writeFile commit could race outside the validated path
Summary
In affected versions of openclaw, the sandbox fs-bridge writeFile commit step used an unanchored container path during the final move into place. An attacker racing parent-path changes inside the sandbox could redirect the committed file outside the validated sandbox path.
Impact
This is a sandbox boundary bypass. In-sandbox code could win a time-of-check-time-of-use race and cause host-approved writeFile operations to land outside the validated writable path within the container mount namespace.
Affected Packages and Versions
openclaw (npm)< 2026.3.112026.3.11Technical Details
The hardening work for anchored remove, rename, and mkdir operations did not fully cover the writeFile commit path. The final mv still used the raw target path, leaving a race window between safety revalidation and the in-container commit step.
Fix
OpenClaw now anchors the writeFile commit path to the canonical parent directory before the final move. The fix shipped in [email protected].
Workarounds
Upgrade to 2026.3.11 or later.
Medium Basis: The source's own band: MODERATE
0, fixed 2026.3.11 (semver)2026.3.11
2026.3.11npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0