# CVE-2026-100597: OpenClaw before 2026.7.1 Path Traversal via Filesystem Race

> Attackers can exploit a race condition to bypass sandbox restrictions and modify host filesystem paths outside the intended mirror root.

- **Severity:** High 8.8 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-6c5g-hrqv-57wr, GHSA-crg9-c62w-j2p5, MINI-hmgg-qvhh-qw56

## What is CVE-2026-100597?

CVE-2026-100597 is a high-severity vulnerability in OpenClaw, published on 26 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenClaw (npm package 'openclaw') before 2026.7.1 is vulnerable to a time-of-check time-of-use race condition in OpenShell local mirror filesystem mutation operations. The remove, mkdir, and rename operations could act on a different filesystem target after OpenClaw completed its sandbox path-safety check, if the path is changed concurrently. An attacker able to win the race can cause a sandboxed operation to delete, create, or rename a host path outside the intended mirror root with the permissions of the OpenClaw process user. This does not require an operator to have granted host filesystem access outside the sandbox. The issue is fixed in 2026.7.1.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2026-100597?


## How do I fix CVE-2026-100597?

Upgrade to a fixed version.

## Is CVE-2026-100597 being exploited?

There is no known exploitation of CVE-2026-100597 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100597 and fix it if it is affected.

What it is: CVE-2026-100597 is a high-severity vulnerability in OpenClaw, published on 26 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100597 in the wild and no public exploit code.

Affected product: OpenClaw. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2026-100597/ (Markdown: https://insights.sbomify.com/CVE-2026-100597/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100597
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100597
- OSV: https://osv.dev/vulnerability/CVE-2026-100597

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100597/
Summaries are generated and may contain mistakes; the official description above is the record.