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-jv6r-27ww-4gw4

GHSA-jv6r-27ww-4gw4: OpenClaw DM pairing-store identities could satisfy group allowlist authorization

Summary

DM pairing-store identities were incorrectly eligible for group allowlist authorization checks, enabling cross-context authorization in group message paths.

Details

In affected versions, group allowlist evaluation could inherit identities from the DM pairing store. A sender approved via DM pairing could satisfy group sender allowlist checks without being explicitly present in groupAllowFrom.

This is an authorization-policy boundary issue between DM pairing and group allowlists.

Affected Packages / Versions

openclaw (npm): affected <= 2026.2.25 (latest published npm version at triage time)
openclaw (npm): patched >= 2026.2.26 (planned next release)

Fix Commit(s)

openclaw/openclaw@8bdda7a651c21e98faccdbbd73081e79cffe8be0
openclaw/openclaw@051fdcc428129446e7c084260f837b7284279ce9

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.26) so once npm release is published, maintainers can publish the advisory without additional metadata edits.

Maintainer Timeline Note

Maintainers landed the initial fix before this report was filed; this report still provided useful independent confirmation of the issue class and exploit path.

OpenClaw thanks @tdjackey for reporting.

(GitHub Advisory)

Miggo Vulnerability Database

→

GHSA-jv6r-27ww-4gw4

GHSA-jv6r-27ww-4gw4:

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 lies in the improper authorization logic for group messages across multiple channel implementations (Mattermost, LINE, iMessage, Telegram). The core issue was that identities from the Direct Message (DM) pairing store (storeAllowFrom) were being used to evaluate authorization for group channels. This allowed a user who was approved for DMs via the pairing mechanism to bypass the explicit group allowlist (groupAllowFrom).

The fix involved two main commits. The first commit (8bdda7a651c21e98faccdbbd73081e79cffe8be0) corrected the logic in several places to ensure that the group allowlist evaluation does not inherit from the DM pairing store. This was done by modifying the resolveEffectiveAllowFromLists function and updating the calling code in monitorMattermostProvider and shouldProcessLineEvent.

The second commit (051fdcc428129446e7c084260f837b7284279ce9) centralized the DM and group authorization logic into a new function, resolveDmGroupAccessWithLists, to prevent similar vulnerabilities in the future. This refactoring was applied to monitorMattermostProvider and resolveIMessageInboundDecision.

The identified vulnerable functions are the ones that either contained the flawed logic directly or used a shared function (resolveEffectiveAllowFromLists) that had the vulnerability, leading to incorrect authorization decisions.

Vulnerable functions

monitorMattermostProvider

extensions/mattermost/src/mattermost/monitor.ts

The function incorrectly included `storeAllowFrom` (DM pairing identities) when constructing the `effectiveGroupAllowFrom` list. This allowed a user authorized for DMs via pairing to also be authorized for group messages, bypassing the explicit group allowlist.

resolveEffectiveAllowFromLists

src/security/dm-policy-shared.ts

This shared function was responsible for creating the authorization lists. It incorrectly merged `storeAllowFrom` (DM pairing identities) into the `effectiveGroupAllowFrom` list, which was then used by multiple channel implementations for group authorization checks.

shouldProcessLineEvent

src/line/bot-handlers.ts

This function used `normalizeAllowFromWithStore` to determine group access, which incorrectly included DM pairing identities (`storeAllowFrom`) in the group allowlist evaluation. The fix replaces this with `normalizeAllowFrom`, which does not include the pairing store.

resolveIMessageInboundDecision

src/imessage/monitor/inbound-processing.ts

This function relied on the vulnerable `resolveEffectiveAllowFromLists` function to determine group authorization. This meant that `storeAllowFrom` from DM pairing was being considered for group access, leading to the vulnerability. The fix was to switch to the new centralized `resolveDmGroupAccessWithLists` function.

buildTelegramMessageContext

src/telegram/bot-message-context.ts

The original implementation for determining the `effectiveGroupAllow` list incorrectly included identities from the DM pairing store. The fix explicitly uses `normalizeAllowFrom` which only considers the group-specific allowlist, preventing the cross-context authorization.

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.

N/A

-

Basic Information

Basic Information

Concerned about an active attack path?

GHSA-jv6r-27ww-4gw4: OpenClaw DM pairing-store identities could satisfy group allowlist authorization

Summary

Details

Affected Packages / Versions

Fix Commit(s)

Release Process Note

Maintainer Timeline Note

GHSA-jv6r-27ww-4gw4:

N/A

-

Basic Information

Basic Information

Is this CVE running in your environment?

Technical Details

Technical Details

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Vulnerability IntelligenceMiggo AI

Unlock WAF rules for this CVE

WAF Protection Rules

WAF Rule

Reasoning

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Technical Details

GHSA-jv6r-27ww-4gw4: OpenClaw DM pairing-store identities could satisfy group allowlist authorization

Summary

Details

Affected Packages / Versions

Fix Commit(s)

Release Process Note

Maintainer Timeline Note

N/A

N/A

Basic Information

Basic Information

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI