# CVE-2026-47393: PraisonAI `deploy --type api` emits a Flask server with authentication disabled by default

> PraisonAI's default API server configuration lacks authentication, allowing unauthenticated attackers to access endpoints and potentially execute code via LLM orchestration.

- **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-8444-4fhq-fxpq, PYSEC-2026-465

## What is CVE-2026-47393?

CVE-2026-47393 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. CVE-2026-44338 (GHSA-6rmh-7xcm-cpxj) documents that PraisonAI ships a code-generator (`praisonai.deploy.api.generate_api_server_code`) that emits a Flask API server with authentication disabled by default. Users who follow the documented quickstart (`praisonai deploy --type api`) get a server that binds to `0.0.0.0` per the recommended sample YAML, exposes `/chat` and `/agents` endpoints, runs `praisonai.run()` on user-supplied JSON input — LLM orchestration with the API key materials present in the process environment, and does not require any authentication. Versions prior to 4.6.40 still ship the generator with `auth_enabled` defaulting to `False`. The fix shape is opt-in via `APIConfig(auth_enabled=True, auth_token=...)`. Version 4.6.40 fixes the issue.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-1188 (Initialization of a Resource with an Insecure Default)

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

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-47393?

Upgrade praisonai to 4.6.40 or later.

## Is CVE-2026-47393 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47393 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-47393 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-47393/ (Markdown: https://insights.sbomify.com/CVE-2026-47393/index.md)
```

## Sources

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

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