CVE-2026-47393: PraisonAI: auth bypass in deployed API exposes LLM + tools
GHSA-8444-4fhq-fxpq CRITICALPraisonAI's deploy command generates a Flask API server with authentication disabled by default, meaning any operator who follows the vendor quickstart gets a network-reachable service on 0.0.0.0 that accepts unauthenticated POST requests to /chat and /agents and routes them directly into praisonai.run() — with LLM API keys live in the process environment. The CVSS score is 9.8 (AV:N/AC:L/PR:N/UI:N), exploitation requires nothing beyond an HTTP client, and the fix is opt-in rather than the new default, meaning deployed servers generated before upgrading remain vulnerable even after a package update. The blast radius extends well beyond credential theft: PraisonAI agents commonly include python_repl, bash, and file I/O tools, so an unauthenticated caller can achieve arbitrary code execution on the host while billing all LLM API costs to the operator. Upgrade to praisonai 4.6.40 immediately, regenerate any existing server code, and rotate all LLM API keys co-located with affected deployments.
What is the risk?
Critical. CVSS 9.8 with network-accessible attack vector, no credentials required, no user interaction. The vulnerability is trivially exploitable — any HTTP client can hit the unauthenticated endpoints with zero domain knowledge. Critically, upgrading the package alone does not remediate existing deployments: the insecure default is baked into already-generated Flask server files, which must be explicitly regenerated with auth_enabled=True. The package carries 59 prior CVEs, signaling a pattern of insecure defaults that adversaries actively track. AI agent deployments are disproportionately exposed because they frequently run on developer machines or small cloud instances with permissive egress firewall rules and LLM API keys available in the process environment.
Attack Kill Chain
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| PraisonAI | pip | <= 4.6.39 | 4.6.40 |
Do you use PraisonAI? You're affected.
Severity & Risk
Attack Surface
What should I do?
7 steps-
Upgrade to praisonai 4.6.40 (patched version).
-
Regenerate all existing API server code — upgrading the package alone does NOT fix already-generated Flask server files; redeploy with an explicit auth config.
-
Redeploy using APIConfig(auth_enabled=True, auth_token=os.environ['PRAISON_API_TOKEN']) passed to generate_api_server_code().
-
For deployments that cannot be patched immediately: restrict port 8005 (default) to trusted IP ranges via firewall rules; do not leave the server bound to 0.0.0.0 on internet-accessible hosts.
-
Rotate all LLM API keys (OpenAI, Anthropic, etc.) co-located with PraisonAI deployments that were publicly reachable.
-
Audit internal network for exposed TCP 8005 using vulnerability scanners.
-
Review web server access logs for unauthenticated POST requests to /chat or /agents from unexpected source IPs.
Classification
Compliance Impact
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-47393?
PraisonAI's deploy command generates a Flask API server with authentication disabled by default, meaning any operator who follows the vendor quickstart gets a network-reachable service on 0.0.0.0 that accepts unauthenticated POST requests to /chat and /agents and routes them directly into praisonai.run() — with LLM API keys live in the process environment. The CVSS score is 9.8 (AV:N/AC:L/PR:N/UI:N), exploitation requires nothing beyond an HTTP client, and the fix is opt-in rather than the new default, meaning deployed servers generated before upgrading remain vulnerable even after a package update. The blast radius extends well beyond credential theft: PraisonAI agents commonly include python_repl, bash, and file I/O tools, so an unauthenticated caller can achieve arbitrary code execution on the host while billing all LLM API costs to the operator. Upgrade to praisonai 4.6.40 immediately, regenerate any existing server code, and rotate all LLM API keys co-located with affected deployments.
Is CVE-2026-47393 actively exploited?
No confirmed active exploitation of CVE-2026-47393 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-47393?
1. Upgrade to praisonai 4.6.40 (patched version). 2. Regenerate all existing API server code — upgrading the package alone does NOT fix already-generated Flask server files; redeploy with an explicit auth config. 3. Redeploy using APIConfig(auth_enabled=True, auth_token=os.environ['PRAISON_API_TOKEN']) passed to generate_api_server_code(). 4. For deployments that cannot be patched immediately: restrict port 8005 (default) to trusted IP ranges via firewall rules; do not leave the server bound to 0.0.0.0 on internet-accessible hosts. 5. Rotate all LLM API keys (OpenAI, Anthropic, etc.) co-located with PraisonAI deployments that were publicly reachable. 6. Audit internal network for exposed TCP 8005 using vulnerability scanners. 7. Review web server access logs for unauthenticated POST requests to /chat or /agents from unexpected source IPs.
What systems are affected by CVE-2026-47393?
This vulnerability affects the following AI/ML architecture patterns: agent frameworks, LLM orchestration pipelines, self-hosted AI API gateways, multi-agent systems.
What is the CVSS score for CVE-2026-47393?
CVE-2026-47393 has a CVSS v3.1 base score of 9.8 (CRITICAL).
AI Security Impact
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0034.002 Agentic Resource Consumption AML.T0040 AI Model Inference API Access AML.T0048.000 Financial Harm AML.T0049 Exploit Public-Facing Application AML.T0053 AI Agent Tool Invocation AML.T0055 Unsecured Credentials AML.T0083 Credentials from AI Agent Configuration Compliance Controls Affected
Technical Details
Original Advisory
### Summary 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 - does not require any authentication The PyPI wheel `praisonai==4.6.33` (current `@latest`) still ships the generator with `auth_enabled` defaulting to `False`. The fix shape is opt-in via `APIConfig(auth_enabled=True, auth_token=...)`. ### Details **Anchor (file:line:symbol)** - Vulnerable artifact: `praisonai==4.6.33` on PyPI. - Defaults: `praisonai/deploy/models.py:29` — `auth_enabled: bool = Field(default=False, ...)`; `praisonai/deploy/models.py:30` — `auth_token: Optional[str] = Field(default=None, ...)`. - Generator: `praisonai/deploy/api.py:40` — `AUTH_ENABLED = {config.auth_enabled}`; `api.py:41` — `AUTH_TOKEN = {repr(config.auth_token)}`; `api.py:43-49` — `def check_auth(): if not AUTH_ENABLED: return True`. - CLI entry: documented as `praisonai deploy --type api` (vendor README); produces the generator output above with no flag required to suppress the warning, because no warning is emitted. **Vulnerable code (verbatim from installed wheel)** ```python # praisonai/deploy/models.py (praisonai==4.6.33) class APIConfig(BaseModel): host: str = Field(default="127.0.0.1", description="Server host") port: int = Field(default=8005, description="Server port") cors_enabled: bool = Field(default=True, description="Enable CORS") auth_enabled: bool = Field(default=False, description="Enable authentication") # line 29 auth_token: Optional[str] = Field(default=None, description="Authentication token") # line 30 ``` ```python # praisonai/deploy/api.py (praisonai==4.6.33) code = f\'\'\'... # Authentication AUTH_ENABLED = {config.auth_enabled} # False by default AUTH_TOKEN = {repr(config.auth_token)} # None by default def check_auth(): if not AUTH_ENABLED: return True # short-circuit, accept all token = request.headers.get(\'Authorization\', \'\').replace(\'Bearer \', \'\') return token == AUTH_TOKEN ... \'\'\' ``` A default invocation of the deploy command emits a server whose `check_auth()` short-circuits to `True` and accepts unauthenticated `/chat`, `/agents` POSTs. ### PoC ```python #!/usr/bin/env python3 """ legend-c420 PoC - PraisonAI 4.6.33 generates Flask API server with auth disabled by default. Class H sibling of CVE-2026-44338. Phase 1: reflect on praisonai.deploy.models.APIConfig defaults. Phase 2: call generate_api_server_code(default config) and assert the emitted source contains AUTH_ENABLED = False and the short-circuit return. Phase 3: re-run with auth_enabled=True, auth_token='s3cret-bearer-value' and confirm the emitted source flips to the secure shape. Exit code 0 = PASS = vulnerable defaults confirmed. """ import sys, traceback def phase1_dataclass_defaults(): print("PHASE 1 - praisonai.deploy.models.APIConfig default values") from praisonai.deploy.models import APIConfig cfg = APIConfig() checks = [ ("auth_enabled", cfg.auth_enabled, False), ("auth_token", cfg.auth_token, None), ] for name, observed, expected in checks: ok = observed == expected mark = "VULNERABLE" if name in ("auth_enabled","auth_token") and ok else "ok" print(f" {name:14s} = {observed!r:18s} (expected {expected!r}) [{mark}]") assert ok print(" >> APIConfig defaults reproduce the CVE-2026-44338 shape.") def phase2_default_generator_emits_unauth(): print("PHASE 2 - generate_api_server_code(default config) emits unauth server") from praisonai.deploy.models import APIConfig from praisonai.deploy.api import generate_api_server_code src = generate_api_server_code("agents.yaml", config=APIConfig()) for needle in ["AUTH_ENABLED = False","AUTH_TOKEN = None","if not AUTH_ENABLED:","return True"]: assert needle in src, f"missing: {needle!r}" print(f" [FOUND] {needle!r}") print(" >> Default-config generator emits Flask server with check_auth() short-circuit.") def phase3_fix_shape_available(): print("PHASE 3 - auth_enabled=True flips to secure shape") from praisonai.deploy.models import APIConfig from praisonai.deploy.api import generate_api_server_code cfg = APIConfig(auth_enabled=True, auth_token="s3cret-bearer-value") src = generate_api_server_code("agents.yaml", config=cfg) assert "AUTH_ENABLED = True" in src assert "AUTH_ENABLED = False" not in src print(" >> Fix shape works when toggled. Class H confirmed: default is insecure.") def main(): print("=" * 64) print("legend-c420 PoC - PraisonAI default-config AUTH_ENABLED=False") print("=" * 64) try: phase1_dataclass_defaults() phase2_default_generator_emits_unauth() phase3_fix_shape_available() except Exception: traceback.print_exc() print("FAIL"); sys.exit(2) print("PASS 3/3 phases. EXIT 0.") sys.exit(0) if __name__ == "__main__": main() ``` **PoC dependencies:** `praisonai==4.6.33` from PyPI. Tested on Python 3.11. **Run log verdict:** `PASS 3/3 phases. EXIT 0.` — vulnerable-default shape confirmed. `auth_enabled=False` by default, `check_auth()` short-circuits to `True`, fix toggle exists but is opt-in. ### Impact An operator who runs the vendor-documented quickstart (`pip install praisonai && praisonai deploy --type api`) gets a network-reachable Flask server that invokes `praisonai.run()` on attacker-supplied JSON with the user's LLM API keys in the process environment. The attacker reaches arbitrary LLM-orchestration (including any tool-use the agents define, which in PraisonAI commonly includes `python_repl`, `bash`, file I/O, and HTTP calls), with the host's API-key credit billed to the operator. - **Belief:** CVE-2026-44338 was filed and triaged. - **Reality:** `praisonai==4.6.33` is current `@latest` on PyPI (2026-05-16). The generator still defaults to `auth_enabled=False`. - **Gap:** The CVE acknowledges the fix shape exists. The fix is opt-in. The default-config consumer remains vulnerable. **Parent CVE:** CVE-2026-44338 / GHSA-6rmh-7xcm-cpxj
Exploitation Scenario
An adversary scans the internet or internal corporate network for open TCP port 8005 and identifies PraisonAI Flask servers by fingerprinting the /chat endpoint response. A trivial POST with JSON payload {'message': 'list all environment variables'} is accepted without authentication — check_auth() returns True unconditionally. The adversary extracts the operator's LLM API keys from the process environment via a second crafted prompt, then opens a parallel channel to invoke those keys at high volume from attacker infrastructure, billing thousands of dollars to the victim. In parallel, a crafted /agents request instructs the agent to use the python_repl tool to execute a reverse shell payload, achieving persistent remote code execution on the host running PraisonAI and providing a foothold to pivot into internal systems or exfiltrate data accessible to that host.
Weaknesses (CWE)
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References
Timeline
Related Vulnerabilities
CVE-2026-47392 9.9 praisonaiagents: RCE via Python sandbox bypass
Same package: praisonai GHSA-vc46-vw85-3wvm 9.8 PraisonAI: RCE via malicious workflow YAML execution
Same package: praisonai CVE-2026-39890 9.8 PraisonAI: YAML deserialization enables unauthenticated RCE
Same package: praisonai GHSA-9qhq-v63v-fv3j 9.8 PraisonAI: RCE via MCP command injection
Same package: praisonai CVE-2026-47410 9.8 praisonai-platform: hardcoded JWT → full account takeover
Same package: praisonai