PraisonAI call server exposes unauthenticated agent listing, invocation, and deletion when CALL_SERVER_TOKEN is unset
CVE-2026-47396 · GHSA-86qc-r5v2-v6x6 · published 2026-05-29
- Severity
- Critical
- CVSS score
- 9.8
- Chance of exploitation (EPSS)
- 0.43%
- Fixed in
- 4.6.40
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Total
- CISA SSVC
If an operator runs the PraisonAI call server without explicitly setting CALLSERVERTOKEN, any reachable client may be able to: enumerate registered agents; read agent metadata; read agent instruction text; invoke agents; trigger downstream tools or external integrations connected to agents; consume model or API budget through repeated invocation; unregister agents and disrupt availability. The impact depends on the deployed agents and their connected tools. For agents wired to external APIs, internal systems, local tools, or privileged actions, this creates a remote unauthenticated control surface. The issue is not limited to information disclosure.
Upgrade praisonai to 4.6.40 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Recommended fixes: 1. Fail closed when CALLSERVERTOKEN is unset. The authentication dependency should reject requests unless authentication is explicitly configured and a valid token is supplied. 2. Refuse to mount the agent invocation router unless authentication is configured. 3. If unauthenticated mode is intended for local development, bind to 127.0.0.1 by default when CALLSERVERTOKEN is absent. 4. Add a startup error or highly visible warning when the call server is started without authentication. 5. Add regression tests that assert 401 Unauthorized for all sensitive agent routes when no valid token is supplied. 6.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| praisonai | PyPI | <= 4.6.39 | 4.6.40 |
1 registered MCP server installs an affected version today, by the dependency versions a fresh install resolves.
- io.github.MervinPraison/praisonaipraisonai@2.3.42
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- CriticalPraisonAI: AICoder Arbitrary File Write and Command Execution via LLM Tool Callspraisonai
- CriticalPraisonAI: Code Injection via f-string Interpolation in Deploy API Server Generationpraisonai
- CriticalPraisonAI has a Browser Server WebSocket origin validation bypass via unanchored regex (patch bypass of CVE-2026-40289 / GHSA-8x8f-54wf-vv92praisonai
- CriticalPraisonAI: Arbitrary File Read/Write via `multiedit` Tool Without Path Validationpraisonai
- CriticalPraisonAI: Unauthenticated RCE via Jobs API + Approval Bypasspraisonaiagents, praisonai
- CriticalPraisonAI: AgentOS remains unauthenticated after incomplete fix version and allows remote agent invocationpraisonai
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.