# GHSA-qcc4-p59m-p54m: OpenClaw: Sandbox dangling-symlink alias handling could bypass workspace-only write boundary

> An attacker can bypass sandbox write boundaries via dangling symlinks to modify files outside the workspace.

- **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:** 12 Mar 2026

## What is GHSA-qcc4-p59m-p54m?

GHSA-qcc4-p59m-p54m is a path traversal vulnerability in openclaw, published on 12 Mar 2026. 

### Official description

### 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
- Package: npm `openclaw`
- Affected versions: `<= 2026.2.25`
- Latest published npm version included in affected range: `2026.2.25` (checked on February 26, 2026)
- Patched version (pre-set for release): `2026.2.26`

### Technical 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
- Boundary-confined write operations could be redirected outside the configured workspace/sandbox root.
- Primary impact is integrity of host-side files reachable from that path resolution.

### Fix Commit(s)
- `4fd29a35bb85a1898ebff518364c467058b50e14`

### Release Process Note
`patched_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.

## Which versions are affected by GHSA-qcc4-p59m-p54m?

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


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

## How do I fix GHSA-qcc4-p59m-p54m?

Upgrade openclaw to 2026.2.26 or later.

## Is GHSA-qcc4-p59m-p54m being exploited?

There is no known exploitation of GHSA-qcc4-p59m-p54m in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-qcc4-p59m-p54m and fix it if it is affected.

What it is: GHSA-qcc4-p59m-p54m is a path traversal vulnerability in openclaw, published on 12 Mar 2026. 
Exploitation: There is no known exploitation of GHSA-qcc4-p59m-p54m in the wild and no public exploit code.

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

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-qcc4-p59m-p54m/ (Markdown: https://insights.sbomify.com/GHSA-qcc4-p59m-p54m/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-qcc4-p59m-p54m

---
From sbomify Insights: https://insights.sbomify.com/GHSA-qcc4-p59m-p54m/
Summaries are generated and may contain mistakes; the official description above is the record.