When Slack DMs are configured with dmPolicy=open, the Slack slash-command handler incorrectly treated any DM sender as command-authorized. This allowed any Slack user who could DM the bot to execute privileged slash commands via DM, bypassing intended allowlist/access-group restrictions.
openclaw (npm)<= 2026.2.13channels.slack.dm.policy: open (aka dmPolicy=open)Any Slack user in the workspace who can DM the bot could invoke privileged slash commands via DM.
The slash-command path now computes CommandAuthorized for DMs using the same allowlist/access-group gating logic as other inbound paths.
Fix commit(s): - f19eabee54c49e9a2e264b4965edf28a2f92e657
patched_versions is set to the planned next release (2026.2.14). Once that npm release is published, this advisory should be published.
Thanks @christos-eth for reporting.
{
"github_reviewed_at": "2026-02-18T00:51:03Z",
"severity": "MODERATE",
"cwe_ids": [
"CWE-285"
],
"github_reviewed": true,
"nvd_published_at": null
}