Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8amended

PraisonAI call server exposes unauthenticated agent listing, invocation, and deletion when CALL_SERVER_TOKEN is unset

CVE-2026-47396GHSA-86qc-r5v2-v6x6

What to do

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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-47396: 0.43% estimated exploitation activity in the next 30 days; percentile 37.88 (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.

Summary PraisonAI's call server exposes a network-facing agent control API without authentication when CALLSERVERTOKEN is not configured. The affected component is the praisonai.api.agentinvoke router as mounted by praisonai.api.call. The authentication helper verifytoken() fails open when CALLSERVERTOKEN is unset. Since every sensitive agent-control endpoint depends on this helper, starting the call server without a token allows any reachable client to list agents, inspect agent metadata and instructions, invoke agents, and unregister agents. This is security-relevant because the bundled call server includes the vulnerable router and binds to 0.0.0.0. As a result, operators who launch the call server without explicitly setting CALLSERVERTOKEN may unintentionally expose an unauthenticated remote agent control plane. Details The vulnerable behavior is caused by a fail-open authentication default. In praisonai/api/agentinvoke.py, CALLSERVERTOKEN is read from the environment: The…

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

    Amended from ghsa record GHSA-86qc-r5v2-v6x6

  2. Revision 2 · amended ·

    Amended from osv record GHSA-86qc-r5v2-v6x6

  3. Revision 1 · created ·

    Published from ghsa record GHSA-86qc-r5v2-v6x6

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

Advisory: PraisonAI call server exposes unauthenticated agent listing, invocation, and deletion when CALL_SERVER_TOKEN is unset
IDs: CVE-2026-47396, GHSA-86qc-r5v2-v6x6
Record: https://patchnext.com/advisories/cve-2026-47396 (revision 3, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
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.40. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonai: affected <= 4.6.39; fixed in 4.6.40

## 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-86qc-r5v2-v6x6 (GitHub-reviewed advisory GHSA-86qc-r5v2-v6x6 lists affected ranges: PyPI praisonai >=0 <=4.6.39)
- Verified: https://osv.dev/vulnerability/GHSA-86qc-r5v2-v6x6 (OSV record GHSA-86qc-r5v2-v6x6 lists affected ranges: PyPI praisonai >=0 <4.6.40 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…