Answer in brief
CVE-2026-100582 records a High severity (CVSS 7.1) vulnerability in OpenClaw Channel Plugins before 2026.8.1 Channel Read Allowlist Bypass. The current sources do not mark it as known exploited. The current feed maps openclaw/feishu (generic), openclaw/googlechat (generic), openclaw/matrix (generic), openclaw/msteams (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps openclaw/feishu (generic), openclaw/googlechat (generic), openclaw/matrix (generic), openclaw/msteams (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| openclaw/feishugeneric | >=0 <2026.8.1 | 2026.8.1 |
| openclaw/googlechatgeneric | >=0 <2026.8.1 | 2026.8.1 |
| openclaw/matrixgeneric | >=0 <2026.8.1 | 2026.8.1 |
| openclaw/msteamsgeneric | >=0 <2026.8.1 | 2026.8.1 |
Published upstream
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 26, 2026
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.
Quoted source text, attributed separately from HOL analysis.