PraisonAI includes a code-generator (`praisonai.deploy.api.generate_api_server_code`) that produces a Flask API server with authentication disabled by default (`auth_enabled=False`). The default quickstart configuration binds the server to all network interfaces (0.0.0.0) and exposes endpoints such as `/chat` and `/agents` without requiring authentication. This allows unauthenticated access to critical functions, including running `praisonai.run()` with user-supplied JSON input, which can expose API key materials and sensitive orchestration controls. Versions prior to 4.6.40 are affected. The vulnerability is addressed in version 4.6.40 by making authentication opt-in and requiring an auth token.

An attacker can access critical API endpoints without authentication, leading to full confidentiality, integrity, and availability compromise of the PraisonAI service. This includes unauthorized execution of commands and potential exposure of API keys and sensitive orchestration data. The CVSS 3.1 base score is 9.8 (critical), reflecting network attack vector, no privileges required, no user interaction, and high impact on confidentiality, integrity, and availability.

Upgrade PraisonAI to version 4.6.40 or later, where authentication is enabled by default via `APIConfig(auth_enabled=True, auth_token=...)`. Users should avoid deploying the API server with the default quickstart configuration that disables authentication. Since this is not a cloud service, remediation requires user action to upgrade and configure authentication properly. Patch status is confirmed fixed in 4.6.40.