# CVE-2026-100560: OpenClaw before 2026.8.1 Reusable Exec Approvals Authorization Bypass

> Attackers can bypass command approval prompts in OpenClaw by reusing executable paths with different arguments, enabling unauthorized code execution.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **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-74gc-hg2m-79p9, GHSA-xp58-99vr-2354, MINI-48v6-4vc9-hrpj

## What is CVE-2026-100560?

CVE-2026-100560 is a high-severity authentication bypass vulnerability in OpenClaw, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

OpenClaw versions before 2026.8.1 contain an authorization bypass vulnerability where Allow Always approvals for exact commands persist as path-only grants on macOS and Linux. Attackers can reuse the same executable with different arguments to execute commands without triggering new approval prompts, potentially accessing files or internal services.

Weakness: CWE-863 (Incorrect Authorization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-100560 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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