CVE-2026-28392

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.

Affected Packages / Versions

• Package: openclaw (npm)
• Affected versions: <= 2026.2.13
• Affected configuration: Slack DMs enabled with channels.slack.dm.policy: open (aka dmPolicy=open)

Release Process Note

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.

Any Slack user in the workspace who can DM the bot could invoke privileged slash commands via DM.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-28392 has a CVSS score of 4.8 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.14); upgrading removes the vulnerable code path.

Kodem intelligence

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

1. What is CVE-2026-28392? CVE-2026-28392 is a high-severity incorrect authorization vulnerability in openclaw (npm), affecting versions < 2026.2.14. It is fixed in 2026.2.14. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2026-28392? CVE-2026-28392 has a CVSS score of 4.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-28392? openclaw (npm) versions < 2026.2.14 is affected.
4. Is there a fix for CVE-2026-28392? Yes. CVE-2026-28392 is fixed in 2026.2.14. Upgrade to this version or later.
5. Is CVE-2026-28392 exploitable, and should I be worried? Whether CVE-2026-28392 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-28392 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-28392? Upgrade openclaw to 2026.2.14 or later.