# CVE-2026-100594: OpenClaw before 2026.7.1 Authorization Bypass via trajectory export

> Attackers can bypass authorization to access sensitive session data including prompts and tool schemas via the trajectory export endpoint.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/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:** 28 Sep 2026
- **Also known as:** GHSA-89cw-7452-cfrf, GHSA-mwm7-gr2g-859h, MINI-4gm4-28f3-pc7c

## What is CVE-2026-100594?

CVE-2026-100594 is a high-severity missing authorization 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.7.1 contain an authorization bypass vulnerability in the /export-trajectory endpoint that allows non-owner senders to request and receive owner-only trajectory bundles. Attackers can access prompts, model messages, tool schemas, runtime events, and local path metadata from affected sessions by exploiting insufficient authorization checks.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

Upgrade to a fixed version.

## Is CVE-2026-100594 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100594 is a high-severity missing authorization 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-100594 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-100594/ (Markdown: https://insights.sbomify.com/CVE-2026-100594/index.md)
```

## Sources

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

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