CVE-2026-100531: openclaw Slack before 2026.8.1 Authorization Bypass
The @openclaw/slack npm package before 2026.8.1 contains an authorization flaw in its Slack download-file handler: when a file lacks the share metadata used to prove it belongs to the requested conversation, the conversation-authorization check fails open. An authenticated caller restricted to a single conversation who knows or obtains a file identifier can therefore download file contents from outside that conversation's scope, disclosing data across configured conversation boundaries. The issue does not allow listing arbitrary Slack files and does not bypass Slack authentication itself. The issue is fixed in version 2026.8.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
@openclaw/slackto a version that resolves this vulnerability.Fixed in 2026.8.1
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated caller that is restricted to one conversation can exploit it if they know or obtain the identifier of a file outside that conversation. Slack authentication is still required.
What data is exposed and what is not?
The flaw can disclose the contents of files outside the caller's authorized conversation scope when those files lack the share metadata used by the authorization check. It does not allow arbitrary Slack file listing.
Are installations using the fixed package version affected?
No. The issue is fixed in @openclaw/slack version 2026.8.1; affected versions are those before 2026.8.1.