Feishu webhook mode accepted missing encryptKey configuration as valid and blank card-action callback tokens as usable lifecycle tokens. Together, those fail-open paths could allow unauthenticated webhook or card-action traffic to reach command dispatch in affected deployments.
A deployment using Feishu webhook mode without a configured encryptKey, or handling malformed card-action callbacks with blank callback tokens, could fail open instead of rejecting the request. Severity remains critical because affected webhook deployments expose a network-triggered path into OpenClaw command handling without the expected Feishu signature or replay protection.
< 2026.4.152026.4.15OpenClaw 2026.4.15 makes Feishu webhook and card-action validation fail closed. Webhook mode now refuses to start without an encryptKey, missing signing configuration returns invalid instead of valid, invalid signatures return 401, and blank card-action callback tokens are rejected before dispatch.
Verified in v2026.4.15:
extensions/feishu/src/monitor.transport.ts returns invalid when encryptKey is missing, refuses webhook mode without encryptKey, and rejects invalid signatures before JSON handling.extensions/feishu/src/card-action.ts rejects blank callback tokens in the card-action lifecycle guard.extensions/feishu/src/monitor.webhook-security.test.ts covers missing-encryptKey startup and transport rejection.extensions/feishu/src/monitor.card-action.lifecycle.test.ts covers malformed blank-token card actions being dropped before handler dispatch.Fix commit included in v2026.4.15 and absent from v2026.4.14:
c8003f1b33ed2924be5f62131bd28742c5a41aae via PR #66707Thanks to @dhyabi2 for reporting this issue.
{
"cwe_ids": [
"CWE-1188",
"CWE-287",
"CWE-294"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-17T22:32:47Z",
"nvd_published_at": null,
"severity": "CRITICAL"
}