Openclaw cli: OpenClaw has a BlueBubbles group allowlist mismatch via DM pairing-store fallback (CVE-2026-32006)

In OpenClaw CLI (npm package) versions <= 2026.2.25, when BlueBubbles is configured with groupPolicy=allowlist and dmPolicy=pairing, the authorization logic incorrectly treats DM pairing-store identities as if they were group allowlist members. This occurs due to improper composition of DM and group allowlists, allowing a sender authorized only via DM pairing (and not explicitly listed in groupAllowFrom) to pass group sender checks for message and reaction ingress. The root cause is leakage of DM pairing-store identities into group authorization decisions. The fix centralizes authorization composition, removes local recomposition at channel callsites, adds regression tests, and CI guards to prevent future leakage. The vulnerability does not allow bypass of gateway authentication, sandbox boundaries, or host-level privilege escalation beyond existing DM authorization.

Deployments using BlueBubbles with groupPolicy=allowlist and dmPolicy=pairing that have DM pairing-store entries may incorrectly authorize DM-only identities as group members. This could allow unauthorized message or reaction ingress under group checks. However, this does not bypass gateway authentication, sandbox boundaries, or escalate host privileges beyond those already granted by DM authorization.

A patch is available and planned for OpenClaw CLI version 2026.2.26. Users should upgrade to version 2026.2.26 or later once released to resolve this authorization inconsistency. No additional mitigation is required as the issue is constrained to authorization consistency and does not affect other security boundaries.