# CVE-2026-100534: OpenClaw before 2026.8.1 Session Cancellation Authorization Bypass

> Attackers with webhook secrets can cancel unrelated sessions, causing denial of service and bypassing authorization controls in OpenClaw.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/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-g24w-m94m-59qc, GHSA-gg3j-3f24-xwfp, MINI-7xgv-fpmp-36cw

## What is CVE-2026-100534?

CVE-2026-100534 is a low-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.8.1 contain an authorization bypass vulnerability in webhook TaskFlow cancellation that allows attackers to cancel unrelated sessions. An attacker with a webhook route secret can supply an arbitrary child session key to cancel ACP or subagent work outside the route's configured authority.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

Upgrade to a fixed version.

## Is CVE-2026-100534 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100534 is a low-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-100534 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-100534/ (Markdown: https://insights.sbomify.com/CVE-2026-100534/index.md)
```

## Sources

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

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