# CVE-2026-102807: OpenClaw before 2026.9.4 Authorization Bypass via MCP App Standalone Ticket

> Attackers with read-only tokens can bypass authorization to execute write-scoped tools, enabling unauthorized state changes in OpenClaw.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/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:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-3xrq-g42v-gh57, MINI-5hc2-4chg-rpqh

## What is CVE-2026-102807?

CVE-2026-102807 is a medium-severity missing authorization vulnerability in OpenClaw, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenClaw before 2026.9.4 contains an incorrect authorization vulnerability in the mcp.app.view method that allows read-scoped operators to execute MCP App tools requiring operator.write scope. Attackers with operator.read tokens can obtain a standalone ticket from mcp.app.view and redeem it at the MCP app view endpoint to invoke state-changing tools without proper authorization checks.

Weakness: CWE-863 (Incorrect Authorization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-102807 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102807 is a medium-severity missing authorization vulnerability in OpenClaw, published on 29 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-102807 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-102807/ (Markdown: https://insights.sbomify.com/CVE-2026-102807/index.md)
```

## Sources

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

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