openclaw
Affected
- introduced
0, fixed2026.2.26(semver)
Fixed versions
2026.2.26
Fix
- Fixed version
2026.2.26npm install [email protected]
Advisory
Also known as: None
OpenClaw: Sandbox dangling-symlink alias handling could bypass workspace-only write boundary
Summary
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.
Affected Packages / Versions
openclaw<= 2026.2.252026.2.25 (checked on February 26, 2026)2026.2.26Technical Details
In 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.
Impact
Fix Commit(s)
4fd29a35bb85a1898ebff518364c467058b50e14Release Process Notepatched_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.
High Basis: The source's own band: HIGH
0, fixed 2026.2.26 (semver)2026.2.26
2026.2.26npm 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