CVE-2026-57122

PraisonAI: Webhook signature verification skipped (fail-open) when secret unset, allowing forged inbound webhooks (WhatsApp & Linear bots)

Published Sep 14, 2026 CVSS 3.1 · 8.6 High EPSS < 1% KEV · Not listed
Description
PraisonAI is a multi-agent teams system. Prior to 4.6.59, the WhatsApp and Linear bot webhook handlers verify HMAC signatures only when WHATSAPP_APP_SECRET or LINEAR_WEBHOOK_SECRET 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.

Analysis

AI-generated

Technical impact

The vulnerability lies in PraisonAI’s handling of WhatsApp and Linear webhook requests that omits signature verification when the secrets WHATSAPP_APP_SECRET or LINEAR_WEBHOOK_SECRET are not set, allowing unsigned request bodies to be parsed and dispatched. 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 version 4.6.59.

Affected Systems

All installations of PraisonAI earlier than version 4.6.59 that expose the WhatsApp or Linear webhook endpoints are affected. The flaw exists only when WHATSAPP_APP_SECRET or LINEAR_WEBHOOK_SECRET are not set; any deployment that relies on these bots without proper secrets is vulnerable.

Risk and Exploitability

The CVSS score of 8.6 indicates high severity, and the EPSS score is < 1%, indicating a very low yet non‑zero exploitation probability. The flaw is exploitable by any external host that can reach the webhook route. The issue is not listed in CISA KEV, yet the nature of the flaw—remote unauthenticated request forging—implies a high likelihood of abuse, especially in exposed services. Attackers do not need privileges and can abuse the webhook endpoint via HTTP POST with crafted HMAC headers or without any headers at all, thereby bypassing verification entirely.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade PraisonAI to version 4.6.59 or later to apply the signature‑verification fix.
  • Configure WH for each bot and enforce signature validation on all incoming webhook requests.
  • Disable or remove any unused webhook endpoints to reduce the attack surface.

Generated by OpenCVE AI on September 21, 2026 at 00:09 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-x92v-rpx6-p6cw PraisonAI: Webhook signature verification skipped (fail-open) when secret unset, allowing forged inbound webhooks (WhatsApp & Linear bots)
History
Type Values Removed Values Added
First Time appeared Mervinpraison
Mervinpraison praisonai
Vendors & Products Mervinpraison
Mervinpraison praisonai
Type Values Removed Values Added
Description PraisonAI is a multi-agent teams system. Prior to 4.6.59, the WhatsApp and Linear bot webhook handlers verify HMAC signatures only when WHATSAPP_APP_SECRET or LINEAR_WEBHOOK_SECRET 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.
Title PraisonAI: Webhook signature verification skipped (fail-open) when secret unset, allowing forged inbound webhooks (WhatsApp & Linear bots)
Weaknesses CWE-345
CWE-347
References
Metrics cvssV3_1

{'score': 8.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 14, 2026, 6:11 PM
Reserved
Jun 24, 2026, 12:33 AM
Status
Deferred
Published
Sep 14, 2026, 4:17 PM
Modified
Sep 15, 2026, 2:45 PM