# CVE-2026-100527: OpenClaw before 2026.8.2 Denial of Service via Browser Relay

> Unauthenticated attackers can exhaust pending authentication slots in the Browser Relay, preventing legitimate extensions from connecting and causing denial of service.

- **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-2rm8-9g74-xwqp, GHSA-m78m-7h3q-q938, MINI-gvjw-46rc-h3x5

## What is CVE-2026-100527?

CVE-2026-100527 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 before 2026.8.2 contains a denial of service vulnerability in the Browser extension relay that allows unauthenticated network sources to exhaust pending-authentication capacity. Attackers can hold every pending slot by maintaining silent WebSocket upgrades, preventing paired extensions from completing Browser Relay Authentication v2.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

Upgrade to a fixed version.

## Is CVE-2026-100527 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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