N/A

CVSS Score

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

GHSA-72q8-jcmc-97wx

GHSA-72q8-jcmc-97wx: OpenClaw: Feishu card actions could misclassify DMs and skip dmPolicy

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: < 2026.4.20
Patched version: 2026.4.20

Impact

Feishu card-action callbacks could synthesize a message event with DM conversations classified as group conversations. That skipped dmPolicy enforcement for card actions, so a sender in a Feishu DM could trigger card-action flows that should have been blocked by a restrictive DM policy.

The issue is limited to Feishu card-action handling. Severity is medium.

Fix

OpenClaw now resolves Feishu card-action chat type before dispatch, including API lookup when stored context is unavailable, and avoids falling through to group handling for DMs.

Fix commit:

90979d7c3ef7ec30b9f8aa6963a5e38d2f17d166

Release

Fixed in OpenClaw 2026.4.20.

(GitHub Advisory)

Miggo Vulnerability Database

→

GHSA-72q8-jcmc-97wx

GHSA-72q8-jcmc-97wx:

N/A

CVSS Score

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
openclaw	npm	< 2026.4.20	2026.4.20

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability exists in the Feishu card action handling logic within OpenClaw. The root cause is the incorrect assumption that the presence of a chat_id in a Feishu event context implies a 'group' chat. This logic was present in multiple functions, most notably buildSyntheticMessageEvent and handleFeishuCardAction. When a user in a Direct Message (DM) triggered a card action, the application would misclassify the DM as a group chat. This classification error caused the system to skip the dmPolicy enforcement, which should have blocked certain actions in a DM context. An attacker could exploit this to perform actions in a DM that would otherwise be restricted.

The patch addresses this by introducing a new function, resolveCardActionChatType, which explicitly fetches the chat type from the Feishu API when it's not available in the event context. This ensures that DMs are correctly identified, and the appropriate security policies, like dmPolicy, are enforced. The vulnerable functions (handleFeishuCardAction, dispatchSyntheticCommand, and buildSyntheticMessageEvent) were all modified to use this new, more reliable method of determining the chat type.

Vulnerable functions

handleFeishuCardAction

extensions/feishu/src/card-action.ts

This function is the main handler for Feishu card actions. Before the patch, it used a flawed logic `(event.context.chat_id ? "group" : "p2p")` to determine the chat type. This incorrectly classified direct messages (DMs) as group chats if a `chat_id` was present, causing the `dmPolicy` to be bypassed. The function then passed this incorrect chat type to other functions, leading to the vulnerability.

dispatchSyntheticCommand

extensions/feishu/src/card-action.ts

This function was responsible for creating and dispatching a synthetic message event. It was called by `handleFeishuCardAction` and would, in turn, call `buildSyntheticMessageEvent` with a potentially incorrect chat type. The patch adds a call to the new `resolveCardActionChatType` function to correctly determine the chat type before dispatching the message.

buildSyntheticMessageEvent

extensions/feishu/src/card-action.ts

This function contained the core of the vulnerability. It had a fallback logic that assumed if a `chat_id` was present, the chat type was 'group'. This is an incorrect assumption for Feishu DMs, which can also have a `chat_id`. This misclassification led to the `dmPolicy` not being enforced for card actions in DMs. The patch removes this flawed logic and makes the `chatType` parameter mandatory.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.