# CVE-2026-100572: OpenClaw before 2026.8.1 Denial of Service via Rate Limit

> An unauthenticated attacker can exhaust rate limits in OpenClaw behind a reverse proxy, causing denial of service for legitimate Synology Chat webhooks.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Sep 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-fw6q-2frm-jxxr, GHSA-gcvj-pm5f-x5cv, MINI-ch75-55j6-6586

## What is CVE-2026-100572?

CVE-2026-100572 is a medium-severity denial of service vulnerability in OpenClaw, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenClaw versions >= 2026.3.25 and < 2026.8.1 apply invalid-token rate limiting for Synology Chat webhooks before authentication and key the limit on the raw proxy socket address. In deployments where OpenClaw sits behind a trusted reverse proxy or tunnel and multiple external clients share a single socket address, an unauthenticated sender can exhaust the shared invalid-token budget, causing subsequent legitimate Synology Chat webhook callbacks to be rejected until the rate-limit window expires. The attacker cannot obtain a valid token or read message data; the impact is temporary loss of channel availability. Fixed in 2026.8.1.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

Upgrade to a fixed version.

## Is CVE-2026-100572 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100572 is a medium-severity denial of service vulnerability in OpenClaw, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100572 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-100572/ (Markdown: https://insights.sbomify.com/CVE-2026-100572/index.md)
```

## Sources

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

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