GHSA-3jx4-q2m7-r496 OpenClaw: Hardlink alias checks could bypass workspace-only file boundaries in specific configurations

Not scored Published

Attackers can read or modify files outside the workspace via hardlink aliases in OpenClaw when workspace-only restrictions are enabled.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Not stated
Victim action needed
Not needed
Fix
Available

What is GHSA-3jx4-q2m7-r496?

GHSA-3jx4-q2m7-r496 is a path traversal vulnerability in openclaw, published on 4 Mar 2026.

Official description

Summary

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).

Impact

  • Confidentiality: out-of-workspace files could be read through in-workspace hardlink aliases.
  • Integrity: out-of-workspace files could be modified through in-workspace hardlink aliases.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Latest published version at triage time: 2026.2.24
  • Affected range: <= 2026.2.24
  • Planned patched version: 2026.2.25

Fix Commit(s)

  • 04d91d0319b82fd4de91ed05e9fc5219ff2ab64e (main)

Remediation

OpenClaw now rejects hardlinked final-file aliases during workspace boundary validation for:

  • workspace-only path checks (read / write / edit)
  • workspace-only apply_patch read/write paths
  • sandbox mount-root path-safety checks

Regression tests were added for apply_patch, workspace fs tools, and sandbox fs bridge hardlink alias escapes.

OpenClaw thanks @tdjackey for reporting.

Which versions are affected by GHSA-3jx4-q2m7-r496?

2 open source packages ship an affected version, including openclaw.

PackageAffectedFixed in
openclaw npmAll versions2026.2.25
openclaw npmAll versions2026.2.25

How do I fix GHSA-3jx4-q2m7-r496?

Upgrade openclaw to 2026.2.25 or later.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is GHSA-3jx4-q2m7-r496 being exploited?

There is no known exploitation of GHSA-3jx4-q2m7-r496 in the wild and no public exploit code.

Sources

Is GHSA-3jx4-q2m7-r496 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free