A sandbox boundary-validation gap in symlink alias handling allowed certain workspace-only write paths to be treated as in-boundary even when they could resolve outside the workspace/sandbox root.
openclaw<= 2026.2.252026.2.25 (checked on February 26, 2026)2026.2.26In affected versions, dangling symlink hops could be accepted during boundary checks under missing-target conditions. For workspace-only write flows (including apply_patch), this could allow writes to resolve outside the configured workspace/sandbox boundary.
The fix resolves symlink targets through existing ancestors and fails closed when canonical resolution escapes the configured boundary.
4fd29a35bb85a1898ebff518364c467058b50e14patched_versions is pre-set to the planned next release (2026.2.26) so once npm 2026.2.26 is published, the advisory can be published without further field edits.
Thanks @tdjackey for reporting.
{
"cwe_ids": [
"CWE-367",
"CWE-59"
],
"github_reviewed": true,
"nvd_published_at": null,
"severity": "HIGH",
"github_reviewed_at": "2026-03-12T14:21:54Z"
}