CVE-2026-100575 openclaw CVE debrief

Who should care

Defenders responsible for OpenClaw Slack instances should assess exposure and prioritize upgrading to version 2026.8.1 or later. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify instance versions and exposure. They should also review compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

Defenders should care about CVE-2026-100575 because it allows disallowed participants to bypass sender policies and access tools and data granted to Slack agents, potentially leading to unauthorized access and data exposure. OpenClaw Slack instances should be verified for exposure and upgraded to version 2026.8.1 or later.

• Potential unauthorized access to Slack agents and tools
• Possible data exposure due to bypassed sender policies
• Need for verification of instance versions and exposure
• Priority on upgrading to version 2026.8.1 or later

Technical summary

OpenClaw Slack versions before 2026.8.1 fail to properly enforce sender allowlists in multi-person direct messages, allowing disallowed participants to trigger Slack agents and access tools and data granted to those agents. The vulnerability has a CVSS score of 8.7 and is considered HIGH severity. This issue is exploitable via group DM and affects OpenClaw Slack instances prior to version 2026.8.1. Defenders should prioritize verifying exposure of OpenClaw Slack instances and upgrading to version 2026.8.1 or later.

Defensive priority

Defenders should prioritize verifying exposure of OpenClaw Slack instances and upgrading to version 2026.8.1 or later. Inventory checks and compensating controls should be implemented to mitigate potential impacts.

Recommended defensive actions

• Verify OpenClaw Slack instances are running version 2026.8.1 or later
• Implement inventory checks to identify potentially vulnerable instances
• Review and update compensating controls to mitigate potential impacts
• Review relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, CVSS score, and affected versions. However, there is limited information on potential exploitation or victim impact.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.