# CVE-2026-100582: OpenClaw Channel Plugins before 2026.8.1 Channel Read Allowlist Bypass

> Attackers can bypass channel read allowlists to access restricted content or metadata in supported chat platforms via OpenClaw plugins.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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:** 8 Oct 2026
- **Also known as:** GHSA-g7fw-3gjp-g5hf, GHSA-x2gp-w9p4-cpwg, MINI-m2qj-cj2p-mpxv, MINI-qh39-j3r9-hm4x

## What is CVE-2026-100582?

CVE-2026-100582 is a high-severity missing authorization vulnerability in openclaw feishu, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenClaw channel plugins (@openclaw/msteams, @openclaw/feishu, @openclaw/matrix, and @openclaw/googlechat) before 2026.8.1 do not enforce the configured channel read allowlist for caller-supplied explicit read targets in message, reaction, pin, member, and related metadata read actions. A lower-trust sender or a steered agent with access to a channel read action can therefore retrieve content or metadata from channels or rooms excluded by the operator's read policy; the practical impact depends on the permissions held by the connected bot account. The issue is fixed in 2026.8.1.

Weakness: CWE-862 (Missing Authorization)

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

8 open source packages ship an affected version, including @openclaw/feishu, @openclaw/googlechat and @openclaw/matrix.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@openclaw/feishu` | npm | All versions | 2026.8.1 |
| `@openclaw/feishu` | npm | All versions | 2026.8.1 |
| `@openclaw/googlechat` | npm | All versions | 2026.8.1 |
| `@openclaw/googlechat` | npm | All versions | 2026.8.1 |
| `@openclaw/matrix` | npm | All versions | 2026.8.1 |
| `@openclaw/matrix` | npm | All versions | 2026.8.1 |
| `@openclaw/msteams` | npm | All versions | 2026.8.1 |
| `@openclaw/msteams` | npm | All versions | 2026.8.1 |

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

Upgrade @openclaw/feishu to 2026.8.1 or later.

## Is CVE-2026-100582 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100582 is a high-severity missing authorization vulnerability in openclaw feishu, 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-100582 in the wild and no public exploit code.

Affected packages and fixed versions:
- @openclaw/feishu (npm): affected all versions; fixed in 2026.8.1
- @openclaw/feishu (npm): affected all versions; fixed in 2026.8.1
- @openclaw/googlechat (npm): affected all versions; fixed in 2026.8.1
- @openclaw/googlechat (npm): affected all versions; fixed in 2026.8.1
- @openclaw/matrix (npm): affected all versions; fixed in 2026.8.1
- @openclaw/matrix (npm): affected all versions; fixed in 2026.8.1
- @openclaw/msteams (npm): affected all versions; fixed in 2026.8.1
- @openclaw/msteams (npm): affected all versions; fixed in 2026.8.1

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

## Sources

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

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