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

Published Sep 26, 2026
·
Updated

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.

Affected Software

4 affected components
npm/@openclaw/msteams<2026.8.1
npm/@openclaw/feishu<2026.8.1
npm/@openclaw/matrix<2026.8.1
npm/@openclaw/googlechat<2026.8.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade OpenClaw channel plugins (@openclaw/msteams, @openclaw/feishu, @openclaw/matrix, and @openclaw/googlechat) to a version that resolves this vulnerability.

    Fixed in 2026.8.1

Event History

Sep 26, 2026
CVE Published
via MITRE·02:19 AM
Data Sourced
via MITRE·02:19 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Deployments using @openclaw/msteams, @openclaw/feishu, @openclaw/matrix, or @openclaw/googlechat before 2026.8.1 are affected when channel read actions are available and a channel read allowlist is configured. The actual data exposed depends on the permissions of the connected bot account.

2

What does an attacker need to exploit this issue?

A lower-trust sender, or an agent steered by one, needs access to a channel read action and must be able to supply an explicit read target. No user interaction is required.

3

Does configuring a channel read allowlist prevent exploitation?

No. Before 2026.8.1, the affected plugins do not enforce that allowlist for caller-supplied explicit targets in message, reaction, pin, member, and related metadata read actions.

4

What should be done if an immediate upgrade is not possible?

Restrict access to channel read actions and limit the connected bot account's permissions to only the channels and metadata it must access. This reduces the content and metadata available through an allowlist bypass.

5

How can I determine whether I am affected?

Check whether any listed channel plugin is running a version earlier than 2026.8.1, whether channel read actions can be invoked by lower-trust senders or steered agents, and whether the connected bot account can read channels excluded by the configured allowlist.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203