Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.6amended

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

CVE-2026-57122GHSA-x92v-rpx6-p6cw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonai 4.6.59), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI praisonai

    Affected
    <= 4.6.52
    Fixed in
    4.6.59

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
EPSS
  • CVE-2026-57122: 0.19% estimated exploitation activity in the next 30 days; percentile 8.46 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

The WhatsApp and Linear bot adapters verify the inbound webhook HMAC signature only when a secret is configured. When the secret environment variable is unset — the default on a fresh install and common in development — verification is skipped entirely and the webhook body is parsed and dispatched as a genuine, trusted event. A remote, unauthenticated attacker who can reach the bot's webhook endpoint can inject arbitrary platform events. Affected code: WhatsApp - src/praisonai/praisonai/bots/whatsapp.py - init (line 108): self.appsecret = appsecret or os.environ.get("WHATSAPPAPPSECRET", "") - defaults to "" - route (line 246): app.router.addpost(self.webhookpath, self.handlewebhook) - default path "/webhook" - handlewebhook (lines 585-595): if self.appsecret: gates the ENTIRE check; when falsy the body is json.loads()'d and dispatched to processwebhookdata() with no verification. Linear - src/praisonai/praisonai/bots/linear.py - init (line 86): self.signingsecret = signingsecret or…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-x92v-rpx6-p6cw

  2. Revision 1 · created ·

    Published from osv record GHSA-x92v-rpx6-p6cw

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-57122

Advisory: PraisonAI: Webhook signature verification skipped (fail-open) when secret unset, allowing forged inbound webhooks (WhatsApp & Linear bots)
IDs: CVE-2026-57122, GHSA-x92v-rpx6-p6cw
Record: https://patchnext.com/advisories/cve-2026-57122 (revision 2, source checked 26 Oct 2026, 13:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: praisonai 4.6.59. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonai: affected <= 4.6.52; fixed in 4.6.59

## Suggested inspection (read-only)
- `python -m pip show praisonai`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on praisonai.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-x92v-rpx6-p6cw (OSV record GHSA-x92v-rpx6-p6cw lists affected ranges: PyPI praisonai >=0 <4.6.59 (fixed))
- Verified: https://github.com/advisories/GHSA-x92v-rpx6-p6cw (GitHub-reviewed advisory GHSA-x92v-rpx6-p6cw lists affected ranges: PyPI praisonai >=0 <=4.6.52)

Commands are suggestions: review each one before running it.

Loading voting…