# CVE-2026-100533: OpenClaw before 2026.8.1 Path Traversal via Unicode Fallback

> Admitted requesters can read files outside the workspace boundary via Unicode filename fallback in OpenClaw's tools.fs.workspaceOnly feature.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-5rx7-34fw-64qg, GHSA-q8w6-x36h-hhv6, MINI-x593-g7hw-w7pc

## What is CVE-2026-100533?

CVE-2026-100533 is a medium-severity path traversal vulnerability in OpenClaw, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenClaw versions before 2026.8.1 contain a path traversal vulnerability in the tools.fs.workspaceOnly feature where Unicode filename fallback can normalize validated parent directory components. Admitted requesters can exploit canonically equivalent sibling directories to read files outside the configured workspace boundary.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

Upgrade to a fixed version.

## Is CVE-2026-100533 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100533 is a medium-severity path traversal vulnerability in OpenClaw, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100533 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-100533/ (Markdown: https://insights.sbomify.com/CVE-2026-100533/index.md)
```

## Sources

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

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