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.
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.
openclaw (npm)< 2026.3.112026.3.11The 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.
OpenClaw now anchors the writeFile commit path to the canonical parent directory before the final move. The fix shipped in openclaw@2026.3.11.
Upgrade to 2026.3.11 or later.
{
"github_reviewed": true,
"nvd_published_at": null,
"cwe_ids": [
"CWE-367"
],
"github_reviewed_at": "2026-03-13T15:47:15Z",
"severity": "MODERATE"
}