A workspace-only file-system guard mismatch allowed @-prefixed absolute paths to bypass boundary validation in some tool path checks.
When tools.fs.workspaceOnly=true, certain @-prefixed absolute paths (for example @/etc/passwd) could be validated before canonicalization while runtime path handling normalized the prefix differently. In affected code paths this could permit reads outside the intended workspace boundary.
Per SECURITY.md, OpenClaw is primarily a personal-assistant runtime with trusted-user assumptions, and this path is gated behind non-default sandbox/tooling configuration. That reduces practical exposure, but the bypass is still a security bug and is fixed.
openclaw (npm)2026.2.23<= 2026.2.23>= 2026.2.249ef0fc2ff8fa7b145d1e746d6eb030b1bf692260OpenClaw thanks @tdjackey for reporting.
{
"cwe_ids": [
"CWE-180",
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-03T22:11:54Z",
"nvd_published_at": "2026-03-19T22:16:38Z",
"severity": "MODERATE"
}