CVE-2026-57122: PraisonAI: Webhook signature verification skipped (fail-open) when secret unset, allowing forged inbound webhooks (WhatsApp & Linear bots)
PraisonAI is a multi-agent teams system. Prior to 4.6.59, the WhatsApp and Linear bot webhook handlers verify HMAC signatures only when WHATSAPPAPPSECRET or LINEARWEBHOOKSECRET is configured and otherwise parse and dispatch unsigned request bodies. A remote unauthenticated client that reaches the webhook route can forge messages, comments, or agent-session events, impersonate platform users, influence agent prompts and actions, and disrupt bot processing. This issue is fixed in 4.6.59.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
PraisonAIto a version that resolves this vulnerability.Fixed in 4.6.59
Event History
Frequently Asked Questions
Which deployments are exposed to forged webhook requests?
Deployments using the WhatsApp or Linear bot webhook handlers are exposed when the corresponding WHATSAPP_APP_SECRET or LINEAR_WEBHOOK_SECRET is unset and the webhook route is reachable by a remote client.
Does exploitation require credentials or user interaction?
No. A remote unauthenticated client can exploit the issue by sending requests to a reachable affected webhook route; no credentials or user interaction are required.
What can an attacker do with a forged webhook?
An attacker can forge messages, comments, or agent-session events, impersonate platform users, influence agent prompts and actions, and disrupt bot processing.
What should be done if an immediate upgrade is not possible?
Configure WHATSAPP_APP_SECRET and LINEAR_WEBHOOK_SECRET for the webhook handlers in use so that HMAC signature verification is performed. Restricting remote access to the webhook routes also reduces exposure.
How can I determine whether my instance is affected?
Instances prior to 4.6.59 are affected if they use the WhatsApp or Linear webhook handlers and the applicable webhook secret environment variable is unset. Version 4.6.59 contains the fix.