# CVE-2026-100598: OpenClaw before 2026.7.1 Approval Binding Logic Error

> Attackers can exploit approval binding errors to trick approvers into authorizing unauthorized host actions via unrelated message reactions.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:H/AT:P/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:** 28 Sep 2026
- **Also known as:** GHSA-p9cw-vr9c-p446, GHSA-r88x-r7jj-f2cf, MINI-6258-p4qg-45ch

## What is CVE-2026-100598?

CVE-2026-100598 is a high-severity 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 incorrectly binds Signal approval reactions. In affected versions, a reaction intended to resolve a structured approval request could instead attach to ordinary outbound text when unrelated outbound messages and a pending approval are present in the same conversation. As a result, an approver's reaction to unrelated text could be interpreted as approving or denying a pending host action; the practical impact depends on the pending request, conversation timing, and the actions available to the OpenClaw process. The issue does not change the authority of correctly identified approvers. This is fixed in version 2026.7.1.

Weakness: CWE-346 (Origin Validation Error)

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


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

Upgrade to a fixed version.

## Is CVE-2026-100598 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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