Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.6amended

PraisonAI: AgentMail webhook mode accepts forged unsigned message.received events and invokes agents

CVE-2026-61436GHSA-7c92-x8vg-4258

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonai 4.6.78), 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.77
    Fixed in
    4.6.78

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-61436: 0.39% estimated exploitation activity in the next 30 days; percentile 33.19 (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.

AgentMail webhook mode accepts forged unsigned message.received events and invokes agents Summary praisonai AgentMail webhook mode exposes a public aiohttp webhook endpoint that accepts caller-controlled message.received JSON without verifying AgentMail's Svix webhook signatures, then dispatches the forged message into the configured agent session and reply path. Technical Details The affected boundary is webhook authenticity. AgentMail's webhook verification documentation says AgentMail delivers webhooks through Svix and includes svix-id, svix-timestamp, and svix-signature headers. Receivers are expected to verify the raw request body with the endpoint signing secret, commonly stored as AGENTMAILWEBHOOKSECRET, before trusting the event body. AgentMail's documented verified payload examples route on eventtype; the forged payload below intentionally uses PraisonAI's accepted handler shape, type plus data, because that is the shape handleemailwebhook() accepts before any signature…

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

    Amended from ghsa record GHSA-7c92-x8vg-4258

  2. Revision 2 · amended ·

    Amended from osv record GHSA-7c92-x8vg-4258

  3. Revision 1 · created ·

    Published from ghsa record GHSA-7c92-x8vg-4258

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-61436

Advisory: PraisonAI: AgentMail webhook mode accepts forged unsigned message.received events and invokes agents
IDs: CVE-2026-61436, GHSA-7c92-x8vg-4258
Record: https://patchnext.com/advisories/cve-2026-61436 (revision 3, source checked 26 Oct 2026, 13:55 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.78. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonai: affected <= 4.6.77; fixed in 4.6.78

## 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://github.com/advisories/GHSA-7c92-x8vg-4258 (GitHub-reviewed advisory GHSA-7c92-x8vg-4258 lists affected ranges: PyPI praisonai >=0 <=4.6.77)
- Verified: https://osv.dev/vulnerability/GHSA-7c92-x8vg-4258 (OSV record GHSA-7c92-x8vg-4258 lists affected ranges: PyPI praisonai >=0 <4.6.78 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…