CVE-2026-32028

In OpenClaw <= 2026.2.24, Discord direct-message reaction notifications did not consistently apply the same DM authorization checks (dmPolicy / allowFrom) that are enforced for normal DM message ingress.

In restrictive DM setups, a non-allowlisted Discord user who can react to a bot-authored DM message could still enqueue a reaction-derived system event in the session.

This is a reaction-only ingress inconsistency. By itself it does not directly execute commands; practical impact depends on downstream automation/tool policy.

Details

The DM message path already enforces dmPolicy/allowFrom authorization, but the DM reaction-notification path previously allowed event enqueue under reaction mode checks without that same authorization gate.

Fix in main aligns reaction ingress with normal message preflight for Discord DM/group-DM/guild policy boundaries and applies equivalent DM reaction authorization hardening for Slack to keep channel behavior consistent.

Affected Packages / Versions

• npm package: openclaw
• Affected: <= 2026.2.24
• Patched: >= 2026.2.25

Fix Commit(s)

• aedf62ac7e669a89c7b299201bf6537dc6b12e0e

Release Process Note

patched_versions is pre-set to the release (2026.2.25) so after npm release the advisory is published.

Thanks @tdjackey for reporting.

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-32028 has a CVSS score of 3.7 (Medium). 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.25); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-32028? CVE-2026-32028 is a medium-severity incorrect authorization vulnerability in openclaw (npm), affecting versions <= 2026.2.24. It is fixed in 2026.2.25. 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-32028? CVE-2026-32028 has a CVSS score of 3.7 (Medium). 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-32028? openclaw (npm) versions <= 2026.2.24 is affected.
4. Is there a fix for CVE-2026-32028? Yes. CVE-2026-32028 is fixed in 2026.2.25. Upgrade to this version or later.
5. Is CVE-2026-32028 exploitable, and should I be worried? Whether CVE-2026-32028 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-32028 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-32028? Upgrade openclaw to 2026.2.25 or later.