CVE-2026-31998: OpenClaw's Synology Chat dmPolicy=allowlist failed open on empty allowedUserIds, allowing unauthorized agent dispatch
OpenClaw 2026.2.22 and 2026.2.23 had an authorization flaw in the optional synology-chat plugin. With dmPolicy set to allowlist and allowedUserIds empty or unset, the plugin let every sender through to agent dispatch. Upgrade the npm package openclaw to 2026.2.24.
Published Mar 3, 2026 · Updated Mar 20, 2026 · Analysis Oct 31, 2026
What an attacker can do
The plugin's default resolved DM policy is allowlist. A helper in the plugin treated an empty allowedUserIds list as allow-all, and webhook authentication in allowlist mode relied on that helper. An operator who chose allowlist but had not yet filled in the list therefore got open access instead of a closed door.
The attacker needs a way to send messages to the Synology Chat bot or webhook. The CVSS 4.0 vector shows network access with low privileges, so they must at least reach the channel as a Synology user. The advisory points out that the channel plugin must be set up and that sender access is needed.
Once a message passes, it is dispatched to the agent. The agent can then call its tools in response, so an unauthorized sender can trigger downstream actions with whatever tools the agent holds. The flaw does not give code execution directly. It removes the allowlist that was meant to limit who can talk to the agent.
Who is affected
npm package openclaw, versions >= 2026.2.22 and <= 2026.2.23, only if the synology-chat channel plugin is enabled with dmPolicy allowlist and an empty or missing allowedUserIds. Check:
npm ls openclawThen look in your OpenClaw config for the synology-chat section and its allowedUserIds list.
openclaw
- Ecosystem
- npm
- Affected
- >= 2026.2.22, <= 2026.2.23
- Fixed in
- 2026.2.24
- Check
npm ls openclaw
How to fix it
Upgrade to openclaw 2026.2.24, which includes fix commits 0ee30361b8f6ef3f110f3a7b001da6dd3df96bb5 and 7655c0cb3a47d0647cbbf5284e177f90b4b82ddb. The advisory was updated on 2026-02-25 to confirm the release is on npm.
npm install [email protected]The advisory names no workaround. Filling allowedUserIds with the intended user ids closes the gap on affected versions, since the flaw only appears with an empty list.
How to tell if you were hit
Review agent session history for Synology Chat senders that are not in your intended user list, and check whether allowedUserIds was empty while the plugin ran on 2026.2.22 or 2026.2.23. Beam records the shell commands and tool calls an agent made, which shows what an unexpected sender triggered.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
In openclaw versions 2026.2.22 and 2026.2.23, the optional synology-chat channel plugin had an authorization fail-open condition: when dmPolicy was allowlist and allowedUserIds was empty/unset, unauthorized senders were still allowed through to agent dispatch.
This is assessed as medium severity because it requires channel/plugin setup and Synology sender access, but can still trigger downstream agent/tool actions.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
>= 2026.2.22, <= 2026.2.23 - Latest published affected version at patch time:
2026.2.23 - Planned patched version:
2026.2.24
Details
Root cause was a policy mismatch across plugin code paths:
- Default resolved DM policy was
allowlist. - Empty
allowedUserIdswas treated as allow-all. - Webhook auth in allowlist mode depended on that helper.
Result: allowlist with empty list behaved like open access for inbound Synology senders.
Fix Commit(s)
0ee30361b8f6ef3f110f3a7b001da6dd3df96bb57655c0cb3a47d0647cbbf5284e177f90b4b82ddb
Release Process Note
patched_versions is pre-set to the planned next release (>= 2026.2.24). Once npm release 2026.2.24 is published, the advisory can be published directly.
OpenClaw thanks @tdjackey for reporting.
Publication Update (2026-02-25)
[email protected] is published on npm and contains the fix commit(s) listed above. This advisory now marks >= 2026.2.24 as patched.
Credited to tdjackey.
Questions
- Is CVE-2026-31998 relevant if I do not use Synology Chat?
No. The flaw is in the optional synology-chat channel plugin only.
- Which versions are affected?
2026.2.22 and 2026.2.23. Version 2026.2.24 contains the fix.
- What is the bug?
With dmPolicy allowlist and an empty allowedUserIds, the helper treated the empty list as allow-all, so any inbound Synology sender reached the agent.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-62197
OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs
medium8.5Oct 21, 2026CVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026
