CVE-2026-32924: OpenClaw
CVE-2026-32924
OpenClaw before 2026.3.12 contains an authorization bypass vulnerability where Feishu reaction events with omitted chat_type are misclassified as p2p conversations instead of group chats. Attackers ca...
Overview
A critical authorization bypass vulnerability has been identified in OpenClaw, a software integration platform. Tracked as CVE-2026-32924, this flaw has a maximum severity rating of 9.8 on the CVSS scale. It affects all versions of OpenClaw prior to 2026.3.12.
Vulnerability Details
OpenClaw processes reaction events from Feishu, a collaboration platform. The vulnerability exists in how OpenClaw classifies these events. When a reaction event is sent with the chat_type field omitted, the software incorrectly treats it as a private, person-to-person (p2p) message. In reality, the event may originate from a group chat.
This misclassification is exploitable. Attackers can craft malicious reaction events that appear to be p2p, thereby bypassing two critical security controls designed for group chats: groupAllowFrom (which restricts which users can post in a group) and requireMention (which requires a bot to be mentioned before it acts).
Potential Impact
The primary risk is unauthorized access and command execution. An attacker within a Feishu group could use this flaw to:
- Send commands to integrated bots or services that should be restricted to specific users.
- Trigger automated workflows or data retrievals without proper authorization.
- Potentially access sensitive information or systems connected through OpenClaw, depending on its configuration.
This could lead to data exposure, unauthorized actions, and a compromise of integrated systems. For context on how such vulnerabilities can lead to real-world incidents, recent data breach reports are available at breach reports.
Remediation and Mitigation
The vendor has released a fix in OpenClaw version 2026.3.12.
Primary Action: All users must immediately upgrade to OpenClaw 2026.3.12 or later. This update correctly enforces group chat security policies even when the chat_type field is absent.
Temporary Mitigation (If Immediate Patching is Not Possible):
- Review and audit logs for any unexpected reaction event activity from Feishu integrations.
- Consider temporarily restricting high-privilege bot functionalities in group chat environments if feasible within your workflow.
- Isolate OpenClaw instances from accessing the most sensitive downstream systems until the patch is applied.
Stay informed about critical patches and emerging threats by following the latest security news. Proactive patching remains the most effective defense against such critical vulnerabilities.
Never miss a critical vulnerability
Get real-time security alerts delivered to your preferred platform.
Related Advisories
changedetection.io is a free open source web page change detection tool. Prior to 0.54.8, the @login_optionally_required decorator is placed before (outer to) @blueprint.route() instead of after it. I...
PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request ...
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to 4.0.2 and 3.7.11, Workflow templates endpoints allow any client to retrieve Wo...
OpenClaw versions prior to 2026.2.14 contain a privilege escalation vulnerability in the Slack slash-command handler that incorrectly authorizes any direct message sender when dmPolicy is set to open ...