Summary
OpenClaw: Feishu reaction events could bypass group authorization and mention gating
A Feishu reaction-originated synthetic event could misclassify a group conversation as p2p when the inbound reaction payload omitted chat_type. Authorization and mention-gating logic keyed off that incorrect chat type and evaluated the event as a direct message instead of a group message.
Affected versions
openclaw <= 2026.3.11
Impact
This could bypass groupAllowFrom and requireMention protections for reaction-derived events in Feishu group chats.
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Fixed in openclaw 2026.3.12. Reaction events now preserve the correct group context before authorization and mention-gate evaluation. Users should update to 2026.3.12 or later.
Frequently Asked Questions
- What is GHSA-M69H-JM2F-2PV8? GHSA-M69H-JM2F-2PV8 is a medium-severity incorrect authorization vulnerability in openclaw (npm), affecting versions <= 2026.3.11. It is fixed in 2026.3.12. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- Which versions of openclaw are affected by GHSA-M69H-JM2F-2PV8? openclaw (npm) versions <= 2026.3.11 is affected.
- Is there a fix for GHSA-M69H-JM2F-2PV8? Yes. GHSA-M69H-JM2F-2PV8 is fixed in 2026.3.12. Upgrade to this version or later.
- Is GHSA-M69H-JM2F-2PV8 exploitable, and should I be worried? Whether GHSA-M69H-JM2F-2PV8 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-M69H-JM2F-2PV8 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-M69H-JM2F-2PV8? Upgrade
openclawto 2026.3.12 or later.