# GHSA-xmv6-r34m-62p4: OpenClaw: Sandbox media fallback tmp symlink alias bypass allows host file reads outside sandboxRoot

> An attacker can read arbitrary host files outside the sandbox by exploiting a symlink bypass in the temporary directory fallback mechanism.

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

## What is GHSA-xmv6-r34m-62p4?

GHSA-xmv6-r34m-62p4 is a path traversal vulnerability in openclaw, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Summary
A sandbox path validation bypass in `openclaw` allows host file reads outside `sandboxRoot` via the media path fallback tmp flow when the fallback tmp root is a symlink alias.

### Affected Packages / Versions
- Package: `npm openclaw`
- Affected versions: `<= 2026.2.24`
- Latest published npm version at triage time (February 26, 2026): `2026.2.24`
- Patched version : `2026.2.25`

### Details
When `/tmp/openclaw` is unavailable or unsafe, `resolvePreferredOpenClawTmpDir()` in `src/infra/tmp-openclaw-dir.ts` fell back to `os.tmpdir()/openclaw-<uid>` without verifying that fallback path was a trusted non-symlink directory.

`resolveSandboxedMediaSource()` (`src/agents/sandbox-paths.ts`) allows absolute tmp media paths under the OpenClaw tmp root using lexical containment and alias checks. If the fallback tmp root is a symlink alias (for example to `/`), inputs like `$TMPDIR/openclaw-<uid>/etc/passwd` can pass validation and resolve to host files outside `sandboxRoot`.

### Impact
This can break sandbox media path confinement and permit unauthorized host file reads (confidentiality impact).

### Reproduction (high level)
1. Force resolver fallback (make `/tmp/openclaw` unavailable/invalid).
2. Make fallback root (`$TMPDIR/openclaw-<uid>`) a symlink alias to `/`.
3. Submit media path under fallback root (for example `$TMPDIR/openclaw-<uid>/etc/passwd`).
4. Observe accepted path and read outside `sandboxRoot`.

### Fix Commit(s)
- `496a76c03ba85e15ea715e5a583e498ae04d36e3`

### Release Process Note
Patched version is pre-set to release `2026.2.25`; once npm publish for `2026.2.25` is complete, this advisory can be published without further metadata edits.

OpenClaw thanks @tdjackey for reporting.

## Which versions are affected by GHSA-xmv6-r34m-62p4?

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-xmv6-r34m-62p4?

Upgrade openclaw to 2026.2.25 or later.

## Is GHSA-xmv6-r34m-62p4 being exploited?

There is no known exploitation of GHSA-xmv6-r34m-62p4 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-xmv6-r34m-62p4 and fix it if it is affected.

What it is: GHSA-xmv6-r34m-62p4 is a path traversal vulnerability in openclaw, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-xmv6-r34m-62p4 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-xmv6-r34m-62p4/ (Markdown: https://insights.sbomify.com/GHSA-xmv6-r34m-62p4/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-xmv6-r34m-62p4

---
From sbomify Insights: https://insights.sbomify.com/GHSA-xmv6-r34m-62p4/
Summaries are generated and may contain mistakes; the official description above is the record.