CVE-2026-32924: Openclaw Auth Bypass Vulnerability

CVE-2026-32924 Overview

OpenClaw before version 2026.3.12 contains an authorization bypass vulnerability affecting the handling of Feishu reaction events. When reaction events omit the chat_type field, they are incorrectly classified as peer-to-peer (p2p) conversations instead of group chats. This misclassification allows attackers to bypass critical security protections including groupAllowFrom and requireMention controls that are designed to restrict access in group chat environments.

Critical Impact

Attackers can exploit this authorization bypass to circumvent group chat security restrictions, potentially gaining unauthorized access to protected group conversations and bypassing mention-based authentication requirements.

Affected Products

• OpenClaw versions prior to 2026.3.12
• OpenClaw Node.js implementations with Feishu integration
• Deployments utilizing groupAllowFrom or requireMention protections

Discovery Timeline

• 2026-03-29 - CVE-2026-32924 published to NVD
• 2026-03-31 - Last updated in NVD database

Technical Details for CVE-2026-32924

Vulnerability Analysis

This vulnerability stems from improper authorization handling (CWE-863) in OpenClaw's Feishu event processing logic. When processing reaction events from Feishu, the application relies on the chat_type field to determine whether an event originated from a group chat or a direct peer-to-peer conversation. However, the application fails to handle the case where this field is omitted from incoming events.

The security impact is significant because OpenClaw implements distinct security controls for group versus p2p contexts. The groupAllowFrom restriction limits which users can interact with the bot in group settings, while requireMention enforces that the bot must be explicitly mentioned before processing commands in groups. By causing events to be misclassified as p2p conversations, attackers effectively bypass both of these protective mechanisms.

Root Cause

The root cause is improper input validation and default value handling in the event classification logic. When the chat_type field is absent from a Feishu reaction event payload, the application defaults to treating it as a p2p conversation rather than failing safely or requiring explicit classification. This violates the principle of secure defaults and allows malicious actors to craft events that circumvent group-specific authorization controls.

Attack Vector

The attack is network-based and requires no authentication or user interaction to execute. An attacker with the ability to send crafted Feishu reaction events can exploit this vulnerability by:

1. Constructing a reaction event payload that intentionally omits the chat_type field
2. Targeting a group chat where the attacker would normally be restricted by groupAllowFrom or requireMention policies
3. Sending the malformed event to the OpenClaw instance
4. The event is misclassified as a p2p conversation, bypassing group security controls
5. The attacker gains unauthorized access to execute actions that should be restricted in the group context

The vulnerability mechanism involves the event classification logic failing to properly validate the presence of the chat_type field. When this field is omitted, the default classification behavior incorrectly assumes a p2p context, allowing group-originated events to bypass authorization checks. Technical details are available in the GitHub Security Advisory.

Detection Methods for CVE-2026-32924

Indicators of Compromise

• Feishu reaction events processed without a chat_type field in application logs
• Unexpected p2p event classifications for interactions that originated in group contexts
• Users bypassing groupAllowFrom restrictions to access protected group functionality
• Bot responses in group chats that should have required explicit mentions

Detection Strategies

• Implement logging to capture all incoming Feishu events and flag those missing the chat_type field
• Monitor for anomalous patterns where users restricted by groupAllowFrom are successfully interacting with the bot in group contexts
• Audit authentication and authorization logs for bypassed requireMention checks
• Deploy application-layer monitoring to detect malformed event payloads

Monitoring Recommendations

• Enable verbose logging for Feishu event processing to capture all incoming event fields
• Set up alerts for any events classified as p2p that originate from group chat contexts
• Monitor for sudden increases in p2p-classified events that may indicate exploitation attempts
• Review access patterns for users who should be restricted by group authorization policies

How to Mitigate CVE-2026-32924

Immediate Actions Required

• Upgrade OpenClaw to version 2026.3.12 or later immediately
• Review logs for any evidence of exploitation attempts prior to patching
• Audit group authorization configurations to ensure policies are properly enforced
• Consider temporarily disabling Feishu reaction event processing if immediate upgrade is not possible

Patch Information

The vulnerability has been addressed in OpenClaw version 2026.3.12. Users should upgrade to this version or later to remediate the authorization bypass. The fix ensures proper validation of the chat_type field and implements secure default handling when the field is absent. For detailed patch information, refer to the GitHub Security Advisory and the VulnCheck Advisory.

Workarounds

• Implement input validation at the network edge to reject Feishu events missing the chat_type field
• Deploy a reverse proxy or API gateway rule to enforce presence of required fields before events reach OpenClaw
• Temporarily disable reaction event processing in group chats until the patch can be applied
• Implement additional authorization checks at the application layer that do not rely solely on chat_type classification

# Upgrade OpenClaw to the patched version
npm update openclaw@2026.3.12

# Verify the installed version
npm list openclaw