Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-100582 medium CVSS 6.5

OpenClaw channel plugins (@openclaw/msteams, @openclaw/feishu, @openclaw/matrix, and @openclaw...

Summary

Vulnerability reported (CVE-2026-100582). Confidential information can be exposed externally. Mitigation: upgrade to 2026.8.1 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-100582 has been found.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade the affected software to 2026.8.1 or later.
If unsure, ask your IT team or search "CVE-2026-100582" on the vendor's site.

CVE-2026-100582 — CWE-862 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 2026.8.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-862) has been reported.

📍 Affected scope

Check the vendor advisory for the affected versions.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2026.8.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。

  2. 2
    Apply patch patch 
    Upgrade to 2026.8.1

    ステージング環境で 2026.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @openclaw/msteams
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2026.8.1"}]}]
npm @openclaw/feishu
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2026.8.1"}]}]
npm @openclaw/matrix
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2026.8.1"}]}]
npm @openclaw/googlechat
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2026.8.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details