CVE-2026-26328: OpenClaw iMessage group allowlist authorization inherited DM pairing-store identities
With iMessage `groupPolicy=allowlist`, OpenClaw also accepted senders approved through DM pairing as members of the group allowlist. Anyone paired for direct messages could talk to the agent in groups where they were never listed. `openclaw` up to 2026.2.13 is affected. Upgrade to 2026.2.14.
Published Feb 18, 2026 · Updated Feb 20, 2026 · Analysis Oct 31, 2026
What an attacker can do
In src/imessage/monitor/monitor-provider.ts, the value effectiveGroupAllowFrom was built from the static groupAllowFrom list plus storeAllowFrom, the identities saved in the DM pairing store. A sender approved through pairing in a one-to-one chat therefore passed the group check in any group, even when neither the sender nor the chat appeared in groupAllowFrom (CWE-284, CWE-863).
The attacker needs a paired DM identity, which means a low-privilege approval already granted. They can then message the agent in group chats that the operator meant to restrict. Anything the agent does for group senders, such as running tools or answering with private context, is then available to them. The CVSS 3.1 vector rates integrity impact high and no confidentiality impact, score 6.5.
This breaks the separation between DM trust and group trust. Teams that pair many people for DMs and keep a short, deliberate group allowlist are the ones who lose their boundary.
Who is affected
The npm package openclaw at 2026.2.13 or earlier, with the iMessage channel using groupPolicy=allowlist. The advisory text also lists the legacy clawdbot package at 2026.1.24-3 or earlier, while the package data lists clawdbot below 2026.2.14 with 2026.2.14 as the patched version. Check:
npm ls -g openclaw clawdbotThen compare your DM pairing store with your groupAllowFrom list.
openclaw
- Ecosystem
- npm
- Affected
- < 2026.2.14
- Fixed in
- 2026.2.14
- Check
npm ls openclaw
clawdbot
- Ecosystem
- npm
- Affected
- < 2026.2.14
- Fixed in
- 2026.2.14
- Check
npm ls clawdbot
How to fix it
Upgrade to 2026.2.14, the patched version (commits 872079d and 90d1e9c):
npm install -g [email protected]effectiveGroupAllowFrom now uses only groupAllowFrom. Pairing-store identities still count for DMs through effectiveDmAllowFrom, but group access must come from explicit group allowlist config. The advisory lists no workaround. After upgrading, review groupAllowFrom and add anyone who should keep group access.
How to tell if you were hit
List the senders in the DM pairing store and compare them with groupAllowFrom. Any sender present only in the store who has posted in a group, or triggered the agent there, hit the flaw. Check iMessage group transcripts and agent session logs for messages from those identities. After the upgrade, such senders are ignored in groups unless listed.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
Under iMessage groupPolicy=allowlist, group authorization could be satisfied by sender identities coming from the DM pairing store, broadening DM trust into group contexts.
Details
Affected component: src/imessage/monitor/monitor-provider.ts.
Vulnerable logic derived effectiveGroupAllowFrom using both the static group allowlist and DM pairing-store identities (storeAllowFrom). This allowed a sender approved via DM pairing to satisfy group authorization in groups even if the sender/chat was not explicitly present in groupAllowFrom.
This weakens boundary separation between DM pairing and group allowlist authorization.
Affected Packages / Versions
openclaw(npm): affected<= 2026.2.13clawdbot(npm): affected<= 2026.1.24-3
Fix Commit(s)
openclaw/openclaw@872079d42fe105ece2900a1dd6ab321b92da2d59openclaw/openclaw@90d1e9cd71419168b2faa54a759b124a3eacfae7
Thanks @vincentkoc for reporting.
Credited to vincentkoc.
Questions
- Who is affected by CVE-2026-26328?
Deployments that use iMessage with
groupPolicy=allowlistand have approved DM senders through pairing.- Does the fix break DM pairing?
No. Pairing still applies to DMs. Only group authorization stopped using the pairing store.
- Which version fixes it?
2026.2.14 for
openclaw. Affected versions are 2026.2.13 and earlier.- Do I need to change my config after upgrading?
Possibly. Anyone who relied on pairing for group access must now appear in
groupAllowFrom.
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
