CVE-2026-47393: CWE-306: Missing Authentication for Critical Function in MervinPraison PraisonAI
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.
AI Analysis
Technical Summary
PraisonAI's code-generator (`praisonai.deploy.api.generate_api_server_code`) produces a Flask API server with authentication disabled by default. Users following the documented quickstart receive a server binding to all interfaces (0.0.0.0) exposing `/chat` and `/agents` endpoints without requiring authentication. This allows unauthenticated access to LLM orchestration functions that use API key materials present in the environment. Versions prior to 4.6.40 have this insecure default; version 4.6.40 introduces an opt-in authentication configuration (`APIConfig(auth_enabled=True, auth_token=...)`) to remediate the issue.
Potential Impact
The vulnerability allows unauthenticated remote attackers to access critical API endpoints, potentially leading to full compromise of the LLM orchestration environment, exposure of API keys, and unauthorized use or manipulation of the system. The CVSS score of 9.8 reflects the critical confidentiality, integrity, and availability impacts.
Mitigation Recommendations
Upgrade PraisonAI to version 4.6.40 or later, where authentication is enabled by default via configuration. Users should configure `APIConfig(auth_enabled=True, auth_token=...)` to enforce authentication on the generated API server. Since this is a code-generator default setting, users must ensure they do not deploy servers with authentication disabled. Patch status is confirmed fixed in version 4.6.40.
CVE-2026-47393: CWE-306: Missing Authentication for Critical Function in MervinPraison PraisonAI
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.
CVSS v3.1
Score 9.8critical
Affected software
pkg:github/mervinpraison/PraisonAIRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
PraisonAI's code-generator (`praisonai.deploy.api.generate_api_server_code`) produces a Flask API server with authentication disabled by default. Users following the documented quickstart receive a server binding to all interfaces (0.0.0.0) exposing `/chat` and `/agents` endpoints without requiring authentication. This allows unauthenticated access to LLM orchestration functions that use API key materials present in the environment. Versions prior to 4.6.40 have this insecure default; version 4.6.40 introduces an opt-in authentication configuration (`APIConfig(auth_enabled=True, auth_token=...)`) to remediate the issue.
Potential Impact
The vulnerability allows unauthenticated remote attackers to access critical API endpoints, potentially leading to full compromise of the LLM orchestration environment, exposure of API keys, and unauthorized use or manipulation of the system. The CVSS score of 9.8 reflects the critical confidentiality, integrity, and availability impacts.
Mitigation Recommendations
Upgrade PraisonAI to version 4.6.40 or later, where authentication is enabled by default via configuration. Users should configure `APIConfig(auth_enabled=True, auth_token=...)` to enforce authentication on the generated API server. Since this is a code-generator default setting, users must ensure they do not deploy servers with authentication disabled. Patch status is confirmed fixed in version 4.6.40.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-19T19:22:45.729Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5f96f22a4a8d59895fb2db
Added to database: 07/21/2026, 15:57:38 UTC
Last enriched: 07/21/2026, 16:12:12 UTC
Last updated: 07/21/2026, 21:14:56 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.