Authorization bypass via misclassified Feishu reaction events
Published Mar 29, 2026 · Updated Mar 29, 2026
Authorization bypass in OpenClaw before 2026.3.12 allows remote attackers to evade Feishu group controls through reaction events. The reaction-originated synthetic-event handler treats an omitted chat_type as p2p, causing authorization and mention checks to use direct-message context. A Feishu group chat and omitted chat_type are required; the event bypasses groupAllowFrom and requireMention, with no broader impact established.
Summary
What happened
Authorization bypass in OpenClaw before 2026.3.12 allows remote attackers to evade Feishu group controls through reaction events. The reaction-originated synthetic-event handler treats an omitted chat_type as p2p, causing authorization and mention checks to use direct-message context. A Feishu group chat and omitted chat_type are required; the event bypasses groupAllowFrom and requireMention, with no broader impact established.
The record
- CVE
- CVE-2026-32924
- Published
- Mar 29, 2026
- Updated
- Mar 29, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-863, CWE-285, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 29, 2026CVE publishedPublication date reported by the CVE source.
- Mar 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.3.12
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo