# CVE-2026-100554: OpenClaw before 2026.8.1 Canvas Capability Revocation Bypass

> Revoked nodes can retain Canvas access during a grace period, bypassing immediate authorization revocation in OpenClaw.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/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-g697-vv6h-r8hv, GHSA-r8gf-76ch-pvpx, MINI-6xxc-v4qr-2wg3

## What is CVE-2026-100554?

CVE-2026-100554 is a low-severity 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 (npm package 'openclaw') versions >= 2026.5.12 and < 2026.8.1 do not immediately invalidate Canvas HTTP authorization when a paired node is revoked. Node revocation invalidates the WebSocket client, but Canvas HTTP authorization continues to accept and renew the previously granted capability until WebSocket close cleanup completes. As a result, a revoked paired node can continue exercising its Canvas capability against the capability's configured routes during the close grace period. The issue is fixed in 2026.8.1; as a workaround, restart the Gateway after revoking a node that has Canvas access.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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


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

Upgrade to a fixed version.

## Is CVE-2026-100554 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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