CVE-2026-26328: Openclaw Auth Bypass Vulnerability

CVE-2026-26328 Overview

CVE-2026-26328 is an authorization bypass vulnerability in OpenClaw, a personal AI assistant application built on Node.js. Prior to version 2026.2.14, when the iMessage integration is configured with groupPolicy=allowlist, the group authorization mechanism incorrectly accepts sender identities from the DM (Direct Message) pairing store. This flaw allows trust established in direct message contexts to be improperly extended into group contexts, potentially enabling unauthorized users to interact with group conversations.

Critical Impact

Unauthorized users who have DM trust can bypass group allowlist restrictions, potentially accessing or sending messages in group conversations they should not be authorized to participate in.

Affected Products

• OpenClaw versions prior to 2026.2.14 on Node.js
• OpenClaw iMessage integration with groupPolicy=allowlist configuration
• OpenClaw deployments using DM pairing store functionality

Discovery Timeline

• 2026-02-20 - CVE-2026-26328 published to NVD
• 2026-02-26 - Last updated in NVD database

Technical Details for CVE-2026-26328

Vulnerability Analysis

This vulnerability stems from improper access control (CWE-284) in the OpenClaw iMessage monitoring component. The application provides a group policy feature that allows administrators to configure an allowlist of authorized identities that can interact with group conversations. However, the authorization logic contains a flaw where identities stored in the DM pairing store are incorrectly evaluated as valid group participants.

When a message is received in a group context, the application should verify that the sender's identity appears on the configured group allowlist. Instead, the vulnerable code path also accepts identities that have been established through direct message pairings, effectively broadening the scope of DM-level trust into group authorization decisions. This represents a context confusion vulnerability where trust boundaries between DM and group communication modes are not properly enforced.

Root Cause

The root cause lies in the monitor-provider.ts file within the iMessage monitoring subsystem. The authorization function failed to distinguish between DM pairing store identities and group allowlist entries during the identity verification process. The lack of proper type validation and context-aware authorization checks allowed the trust scope to expand beyond its intended boundaries.

Attack Vector

An attacker who has established a DM pairing relationship with the OpenClaw instance can exploit this vulnerability to bypass group allowlist restrictions. The attack requires low privileges (authenticated DM access) and can be performed remotely over the network without user interaction. The primary impact is on integrity, as unauthorized senders can inject messages or commands into group contexts where they should not have access.

   return { body, id, sender };
 }
 
+function isRecord(value: unknown): value is Record<string, unknown> {
+  return Boolean(value) && typeof value === "object" && !Array.isArray(value);
+}
+
+function isOptionalString(value: unknown): value is string | null | undefined {
+  return value === undefined || value === null || typeof value === "string";
+}
+
+function isOptionalStringOrNumber(value: unknown): value is string | number | null | undefined {
+  return (
+    value === undefined || value === null || typeof value === "string" || typeof value === "number"
+  );
+}
+
+function isOptionalNumber(value: unknown): value is number | null | undefined {
+  return value === undefined || value === null || typeof value === "number";
+}
+
+function isOptionalBoolean(value: unknown): value is boolean | null | undefined {
+  return value === undefined || value === null || typeof value === "boolean";
+}
+
+function isOptionalStringArray(value: unknown): value is string[] | null | undefined {
+  return (
+    value === undefined ||
+    value === null ||
+    (Array.isArray(value) && value.every((entry) => typeof entry === "string"))

Source: GitHub Commit 872079d

Detection Methods for CVE-2026-26328

Indicators of Compromise

• Unexpected messages or commands appearing in group conversations from identities not on the group allowlist
• Log entries showing group authorization succeeded for identities that only exist in the DM pairing store
• Anomalous activity patterns where DM-paired identities interact with group contexts

Detection Strategies

• Review OpenClaw logs for authorization decisions in group contexts, specifically looking for identities that bypass allowlist verification
• Audit the DM pairing store and compare against group allowlist configurations to identify potential unauthorized access paths
• Implement monitoring for group message events that originate from identities not explicitly listed in groupPolicy=allowlist configurations

Monitoring Recommendations

• Enable verbose logging for the iMessage monitoring component to capture authorization decisions
• Set up alerts for any group interaction from newly paired DM identities
• Periodically audit the relationship between DM pairing store entries and group allowlist configurations

How to Mitigate CVE-2026-26328

Immediate Actions Required

• Upgrade OpenClaw to version 2026.2.14 or later immediately
• Review current groupPolicy=allowlist configurations and verify all allowed identities are intentionally authorized
• Audit DM pairing store entries and remove any unauthorized or suspicious pairings
• Monitor group conversation logs for any signs of unauthorized access prior to patching

Patch Information

OpenClaw has released version 2026.2.14 that addresses this vulnerability. The fix introduces proper type validation functions in the monitor-provider.ts file that ensure DM pairing store identities are correctly isolated from group allowlist authorization decisions. The patch is available through the official release channels and can be obtained from the GitHub Release v2026.2.14. Additional details are available in the GitHub Security Advisory GHSA-g34w-4xqq-h79m.

Workarounds

• Temporarily disable the iMessage integration if immediate patching is not possible
• Switch from groupPolicy=allowlist to a more restrictive configuration that does not rely on identity-based authorization
• Implement network-level access controls to limit which systems can send messages to the OpenClaw instance

# Configuration example
# Upgrade OpenClaw to patched version
npm update openclaw@2026.2.14

# Verify the installed version
npm list openclaw

# Review current group policy configuration
grep -r "groupPolicy" /path/to/openclaw/config/