How severe is CVE-2026-100582?

No CVSS score has been assigned to CVE-2026-100582 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-100582?

CVE-2026-100582 affects the following packages: @openclaw/msteams (npm), @openclaw/feishu (npm), @openclaw/matrix (npm), @openclaw/googlechat (npm). Ecosystems affected: npm.

How do I fix CVE-2026-100582?

Update @openclaw/msteams to 2026.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-100582 is resolved across your whole dependency graph.

How do I detect CVE-2026-100582 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openclaw/msteams, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-100582 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-100582 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-100582 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-100582?

CVE-2026-100582 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 10th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-100582?

CVE-2026-100582 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-100582 published, and has it been updated?

CVE-2026-100582 was published on September 26, 2026 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-100582 — @openclaw/msteams

Fix: openclaw/openclaw#99905

CVE-2026-100582 is a CWE-862 vulnerability in @openclaw/msteams. A fix is available for @openclaw/msteams — see the affected versions and patch details below.

OpenClaw Channel Plugins before 2026.8.1 Channel Read Allowlist Bypass

Also known asGHSA-g7fw-3gjp-g5hf

Published

Sep 26, 2026

Updated

Oct 21, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-100582.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs10th percentile — riskier than 10% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@openclaw/msteamsnpm

11Kdownloads / week

@openclaw/feishunpm

10Kdownloads / week

@openclaw/matrixnpm

3Kdownloads / week

Description

Summary

Channel read actions could skip target allowlists. In affected versions, explicit read targets in Microsoft Teams, Feishu, Matrix, and Google Chat could reach channels or rooms outside the configured read policy.

This advisory is scoped to caller-supplied targets for message, reaction, pin, member, and related metadata reads in the named plugins. It does not change OpenClaw's trusted-operator model or create per-user isolation within one Gateway.

Impact

A lower-trust sender or steered agent with access to a channel read action could retrieve content or metadata from a target excluded by the operator's channel allowlist. Practical impact depends on the bot account's platform permissions.

Patched Versions

The first stable patched version is 2026.8.1.

Mitigations

upgrade each affected channel plugin to 2026.8.1 or later. Before upgrading, disable explicit-target read actions or limit the connected bot account to allowed channels at the platform level.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@openclaw/msteams`	all versions	2026.8.1`npm install @openclaw/msteams@2026.8.1`
📦npm	`@openclaw/feishu`	all versions	2026.8.1`npm install @openclaw/feishu@2026.8.1`
📦npm	`@openclaw/matrix`	all versions	2026.8.1`npm install @openclaw/matrix@2026.8.1`
📦npm	`@openclaw/googlechat`	all versions	2026.8.1`npm install @openclaw/googlechat@2026.8.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openclaw/msteams, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @openclaw/msteams to 2026.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-100582 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Summary Channel read actions could skip target allowlists. In affected versions, explicit read targets in Microsoft Teams, Feishu, Matrix, and Google Chat could reach channels or rooms outside the configured read policy. This advisory is scoped to caller-supplied targets for message, reaction, pin, member, and related metadata reads in the named plugins. It does not change OpenClaw's trusted-operator model or create per-user isolation within one Gateway. ### Impact A lower-trust sender or steered agent with access to a channel read action could retrieve content or metadata from a targe

O3 Security · Impact-Aware SCA

Is CVE-2026-100582 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works