PraisonAI serve agents --api-key is ignored, allowing unauthenticated remote agent execution
CVE-2026-55534 · GHSA-7ww9-85pg-cv4x · published 2026-08-25
- Severity
- High
- CVSS score
- 8.6
- Chance of exploitation (EPSS)
- 0.45%
- Fixed in
- 4.6.58
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Partial
- CISA SSVC
Any attacker who can reach a praisonai serve agents server can invoke configured agents even when the operator explicitly configured --api-key. Impact depends on the configured agents and their tools, but can include: unauthorized LLM/API usage and provider cost consumption; execution of agent workflows; access to connected tool integrations; reads/writes through file, database, cloud, browser, MCP, or messaging tools; availability impact from repeated or long-running agent invocations. This is especially risky because the documented production pattern recommends using --api- key when binding the server publicly.
Upgrade praisonai to 4.6.58 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.
Fail closed when --api-key is configured and require it on every agent invocation route in the serve agents app. Recommended changes: In createagentsapp(), derive an auth dependency from config.get("apikey"). Apply it to both POST {path} and POST /agents/{agentname}. Prefer Authorization: Bearer . Optionally also support X-API-Key for Use constant-time comparison for the expected key. Clarify or unify the relationship between --api-key and CALLSERVER_TOKEN. Add tests proving:
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| praisonai | PyPI | >= 4.6.34, < 4.6.58 | 4.6.58 |
- 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.