UTC
High

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
What it is

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.

What to do

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:

Affected
PackageRegistryAffectedFixed in
praisonaiPyPI>= 4.6.34, < 4.6.584.6.58

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].