In certain workspace-restricted configurations, OpenClaw could follow hardlink aliases inside the workspace that reference files outside the workspace boundary.
By default, tools.fs.workspaceOnly is off. This primarily affects deployments that intentionally enable workspace-only filesystem restrictions (and workspace-only apply_patch checks).
openclaw (npm)2026.2.24<= 2026.2.242026.2.2504d91d0319b82fd4de91ed05e9fc5219ff2ab64e (main)OpenClaw now rejects hardlinked final-file aliases during workspace boundary validation for:
read / write / edit)apply_patch read/write pathsRegression tests were added for apply_patch, workspace fs tools, and sandbox fs bridge hardlink alias escapes.
OpenClaw thanks @tdjackey for reporting.
{
"cwe_ids": [
"CWE-59",
"CWE-668"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-04T19:21:04Z",
"nvd_published_at": null,
"severity": "HIGH"
}