# CVE-2026-47396: PraisonAI call server exposes unauthenticated agent listing, invocation, and deletion when CALL_SERVER_TOKEN is unset

> Unauthenticated remote attackers can list, invoke, and delete agents if the call server is started without a configured token.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-86qc-r5v2-v6x6, PYSEC-2026-466

## What is CVE-2026-47396?

CVE-2026-47396 is a critical missing authorization vulnerability in MervinPraison PraisonAI, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PraisonAI is a multi-agent teams system. Prior to version 4.6.40, PraisonAI's call server exposes a network-facing agent control API without authentication when `CALL_SERVER_TOKEN` is not configured. The affected component is the `praisonai.api.agent_invoke` router as mounted by `praisonai.api.call`. The authentication helper `verify_token()` fails open when `CALL_SERVER_TOKEN` 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 `CALL_SERVER_TOKEN` may unintentionally expose an unauthenticated remote agent control plane. Version 4.6.40 fixes the issue.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-47396?

3 open source packages ship an affected version, including praisonai and PraisonAI.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `praisonai` | PyPI | All versions | 4.6.40 |
| `praisonai` | PyPI | All versions | 4.6.40 |
| `PraisonAI` | PyPI | All versions | 4.6.40 |

## How do I fix CVE-2026-47396?

Upgrade praisonai to 4.6.40 or later.

## Is CVE-2026-47396 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47396 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47396 and fix it if it is affected.

What it is: CVE-2026-47396 is a critical missing authorization vulnerability in MervinPraison PraisonAI, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47396 exists.

Affected packages and fixed versions:
- praisonai (PyPI): affected all versions; fixed in 4.6.40
- praisonai (PyPI): affected all versions; fixed in 4.6.40
- PraisonAI (PyPI): affected all versions; fixed in 4.6.40

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47396/ (Markdown: https://insights.sbomify.com/CVE-2026-47396/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47396
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47396
- OSV: https://osv.dev/vulnerability/CVE-2026-47396

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47396/
Summaries are generated and may contain mistakes; the official description above is the record.