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

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

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Mar 2026

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openclaw` | npm | All versions | 2026.2.25 |
| `openclaw` | npm | All versions | 2026.2.25 |

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

Upgrade openclaw to 2026.2.25 or later.

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

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-3jx4-q2m7-r496 and fix it if it is affected.

What it is: GHSA-3jx4-q2m7-r496 is a path traversal vulnerability in openclaw, published on 4 Mar 2026. 
Exploitation: There is no known exploitation of GHSA-3jx4-q2m7-r496 in the wild and no public exploit code.

Affected packages and fixed versions:
- openclaw (npm): affected all versions; fixed in 2026.2.25
- openclaw (npm): affected all versions; fixed in 2026.2.25

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-3jx4-q2m7-r496/ (Markdown: https://insights.sbomify.com/GHSA-3jx4-q2m7-r496/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-3jx4-q2m7-r496

---
From sbomify Insights: https://insights.sbomify.com/GHSA-3jx4-q2m7-r496/
Summaries are generated and may contain mistakes; the official description above is the record.