# CVE-2026-100585: OpenClaw before 2026.7.1 Authentication Bypass via MCP Channel

> An authorized non-owner can bypass owner-only checks to approve Claude Code permission prompts, potentially executing actions without consent.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-87g7-76gr-73g8, GHSA-p5g8-m35v-7m82, MINI-2r3c-v39g-fv77

## What is CVE-2026-100585?

CVE-2026-100585 is a high-severity missing authorization vulnerability in OpenClaw, published on 26 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

OpenClaw (npm package `openclaw`) before 2026.7.1 fails to enforce the owner-only authorization requirement for Claude Code permission prompts delivered through the MCP channel bridge. An authorized non-owner channel sender with channel command access can approve or deny a pending permission request intended for the owner, causing the requested action to proceed without owner consent. The practical impact depends on the pending action and the host capabilities requested by the Claude Code run. The issue is fixed in version 2026.7.1.

Weakness: CWE-862 (Missing Authorization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-100585 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100585 is a high-severity missing authorization vulnerability in OpenClaw, published on 26 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-100585 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-100585/ (Markdown: https://insights.sbomify.com/CVE-2026-100585/index.md)
```

## Sources

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

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