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

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
• EPSS 0.8%, percentile 55: FIRST’s model estimates a 0.8% chance of exploitation activity in the next 30 days, higher than 55% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes PraisonAI (PyPI) <= 4.6.39, fixed in 4.6.40. Check your lockfile, including transitive dependencies.

What it is

PraisonAI is a multi-agent teams system. CVE-2026-44338 (GHSA-6rmh-7xcm-cpxj) documents that PraisonAI ships a code-generator (praisonai.deploy.api.generateapiservercode) 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 authenabled defaulting to False. The fix shape is opt-in via APIConfig(authenabled=True, authtoken=...). Version 4.6.40 fixes the issue.

From the GitHub advisory

Summary

CVE-2026-44338 (GHSA-6rmh-7xcm-cpxj) documents that PraisonAI ships a code-generator (praisonai.deploy.api.generateapiservercode) 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 - does not require any authentication

The PyPI wheel praisonai==4.6.33 (current @latest) still ships the generator with authenabled defaulting to False. The fix shape is opt-in via APIConfig(authenabled=True, authtoken=...).

Details

Weakness type: CWE-306, CWE-1188.

Product: PraisonAI (PyPI) · Assigned by: GitHub_M · Published: 2026-07-21

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation poc, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 0.78% probability of exploitation activity in the next 30 days; percentile 55.

Timeline

• 2026-05-29 — GitHub-reviewed advisory GHSA-8444-4fhq-fxpq published (critical)
• 2026-07-21 — CVE record published by GitHub_M
• 2026-07-22 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-8444-4fhq-fxpq github.com
2. CVE.org record CVE-2026-47393 cve.org
3. NVD entry CVE-2026-47393 nvd.nist.gov

Other references from the CVE record and advisory

1. github.com github.com
2. github.com github.com
3. github.com github.com
4. github.com github.com

Critical PyPI advisories · Today’s Security Digest