Skip to content

OpenClaw iMessage group allowlist authorization inherited DM pairing-store identities

Moderate severity GitHub Reviewed Published Feb 15, 2026 in openclaw/openclaw • Updated Feb 20, 2026

Package

npm clawdbot (npm)

Affected versions

< 2026.2.14

Patched versions

2026.2.14
npm openclaw (npm)
< 2026.2.14
2026.2.14

Description

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.13
  • clawdbot (npm): affected <= 2026.1.24-3

Fix Commit(s)

  • openclaw/openclaw@872079d42fe105ece2900a1dd6ab321b92da2d59
  • openclaw/openclaw@90d1e9cd71419168b2faa54a759b124a3eacfae7

Thanks @vincentkoc for reporting.

References

@orlyjamie orlyjamie published to openclaw/openclaw Feb 15, 2026
Published to the GitHub Advisory Database Feb 18, 2026
Reviewed Feb 18, 2026
Published by the National Vulnerability Database Feb 20, 2026
Last updated Feb 20, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(8th percentile)

Weaknesses

Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Learn more on MITRE.

Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. Learn more on MITRE.

CVE ID

CVE-2026-26328

GHSA ID

GHSA-g34w-4xqq-h79m

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.