Disclosed weakness · no CVE recorded

OpenClaw could apply direct-message permissions to a Feishu card from an unclassified chat

OpenClaw · OpenClaw Feishu card actions

First documented disclosure · Review checkpoint

Summary

When OpenClaw could not determine a card’s conversation type, it could route the action under direct-message rules.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The project documented the defect and its repair. The reviewed sources identify no malicious use.

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The fallback assigned a direct-message classification when the chat lookup failed or lacked a type.

Conditions required

A Feishu interactive card includes a chat identifier, and the integration cannot resolve the conversation type.

Potential impact

An action originating in a group could avoid checks for group admission or sender authorization.

Affected versions and configurations

The project has not published a complete affected version range.

Fix and mitigation status

OpenClaw 2026.11.2 includes the fix. The exact first fixed release across all release lines is unverified.

Practical next steps

Update OpenClaw. Confirm that an unresolved conversation type prevents card actions from dispatching commands.

Operating lesson

An unavailable authorization attribute should stop an action that depends on it.

Evidence and limits

The October 1 report and November implementation concern the same classification fallback. The project reports that recognized chat types retain their existing rules.

Sources