Openclaw cli: OpenClaw: Slack thread context could include messages from non-allowlisted senders (CVE-2026-41358)

Before OpenClaw version 2026.4.2, when fetching Slack thread starter and thread-history context via the API, messages from senders not on the effective allowlist could still be included if an allowlisted user replied in the same thread. This allowed non-allowlisted messages to enter the agent context, bypassing sender access controls for Slack thread context. The vulnerability was addressed by filtering Slack thread context by the effective allowlist in commit ac5bc4fb37becc64a2ec314864cca1565e921f2d. The affected package is openclaw (npm), with affected versions from 2026.1.29 up to but not including 2026.4.2. The fix is staged for release in OpenClaw 2026.4.2.

The vulnerability allows non-allowlisted Slack messages to be included in the agent context when an allowlisted user replies in the same thread, effectively bypassing sender access controls on Slack thread context. This does not bypass channel authentication but could expose unintended message content to the model context. The CVSS score is 5.4 (medium severity), indicating limited confidentiality and integrity impact without availability impact.

A patch is available in OpenClaw version 2026.4.2 that filters Slack thread context by the effective sender allowlist. Users should upgrade to version 2026.4.2 or later once it is released. Until then, be aware that sender allowlist controls on Slack thread context may be bypassed. No additional vendor advisory states otherwise.