N/A

CVSS Score

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

GHSA-25pw-4h6w-qwvm

GHSA-25pw-4h6w-qwvm: OpenClaw has a BlueBubbles group allowlist mismatch via DM pairing-store fallback

Summary

In openclaw@2026.2.25, BlueBubbles group authorization could incorrectly treat DM pairing-store identities as group allowlist identities when dmPolicy=pairing and groupPolicy=allowlist.

A sender that was only DM-paired (not explicitly present in groupAllowFrom) could pass group sender checks for message and reaction ingress.

Per OpenClaw's SECURITY.md trust model, this is a constrained authorization-consistency issue, not a multi-tenant boundary bypass or host-privilege escalation.

Affected Packages / Versions

Package: openclaw (npm)
Latest published npm version at triage time: 2026.2.25
Affected versions: <= 2026.2.25
Patched versions: >= 2026.2.26 (planned next release)

Technical Details

Root cause was DM/group allowlist composition where DM pairing-store identities could flow into group authorization decisions.

Fix approach:

centralize DM/group authorization composition via shared resolvers
remove local DM/group list recomposition at channel callsites
add cross-channel regression coverage for message + reaction ingress
add CI guard to block future pairing-store leakage into group auth composition

Impact

Affects deployments using BlueBubbles with groupPolicy=allowlist and dmPolicy=pairing when pairing-store entries are present.
Could allow DM-authorized identities to be treated as group-authorized without explicit groupAllowFrom membership.
Does not bypass gateway auth, sandbox boundaries, or create new host-level privilege beyond existing DM authorization.

Fix Commit(s)

051fdcc428129446e7c084260f837b7284279ce9

Miggo Vulnerability Database

→

GHSA-25pw-4h6w-qwvm

GHSA-25pw-4h6w-qwvm:

N/A

CVSS Score

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
openclaw	npm	<= 2026.2.25	2026.2.26

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability, identified as GHSA-25pw-4h6w-qwvm, is an authorization flaw in OpenClaw where DM-paired identities are incorrectly treated as group-authorized identities. This occurs when dmPolicy is set to pairing and groupPolicy is set to allowlist.

The root cause of the vulnerability lies in the logic used to compose the effective allow-lists for group channels. The function resolveEffectiveAllowFromLists and its channel-specific variants (e.g., resolveMattermostEffectiveAllowFromLists) incorrectly included identities from the DM pairing store (storeAllowFrom) when constructing the allow-list for groups (effectiveGroupAllowFrom).

During runtime, when a message is received in a group channel, a message handler function is invoked. The analysis of the patch 051fdcc428129446e7c084260f837b7284279ce9 shows that functions like monitorMattermostProvider (for Mattermost) and resolveIMessageInboundDecision (for iMessage) were responsible for this message processing. These functions would call the flawed helper functions to check permissions. Because the returned group allow-list was tainted with DM-only identities, the check would pass incorrectly, allowing the message from the unauthorized sender to be processed.

The fix involves removing the flawed helper functions and centralizing the authorization logic into a new function, resolveDmGroupAccessWithLists. This new function correctly isolates the DM and group authorization scopes, ensuring that the DM pairing store is not consulted for group authorization decisions. The patch updates the message processing functions to use this new, secure implementation.

Vulnerable functions

resolveEffectiveAllowFromLists

src/security/dm-policy-shared.ts

This function was responsible for calculating effective allow-lists for different channels. It contained the core flaw where it would incorrectly merge the DM pairing-store identities (`storeAllowFrom`) into the group allow-list (`groupAllowFrom`) when `dmPolicy` was set to `pairing`. This allowed a user authorized for DMs to bypass group authorization checks. The function was removed and replaced by `resolveDmGroupAccessWithLists` as part of the fix.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.