Summary
CVE-2026-57124 is a critical vulnerability in PraisonAI, a multi-agent AI orchestration framework, caused by an unauthenticated API endpoint that permits attackers to execute arbitrary OS commands on the host running the PraisonAI UI service. The flaw combines missing authentication (CWE-306) with OS command injection (CWE-78), and carries a CVSS v3.1 base score of 9.8 (Critical). Any PraisonAI deployment running the default UI with network exposure is at risk of full remote compromise.
Technical details
- Root cause: The PraisonAI UI (Starlette-based application) exposes a
POST /api/mcp/connectendpoint that accepts attacker-suppliedcommandandargsparameters. These values are passed directly into theStdioMCPClient, which spawns a local process using the supplied command, without sanitization or authentication. - Trigger conditions: The service binds to
0.0.0.0by default when started viapraisonai ui,praisonai ui agents,praisonai claw, or any application built withpraisonai.integration.host_app.create_host_app()/build_host_app(), making the endpoint reachable to any network-adjacent or remote client. - Attack vector: Network — no authentication or user interaction is required. An attacker simply issues a crafted HTTP POST request to the exposed endpoint.
- Impact: Successful exploitation results in arbitrary command execution under the privileges of the PraisonAI service account, leading to full compromise of confidentiality, integrity, and availability of the host system.
- This issue is distinct from other related PraisonAI advisories concerning MCP command parsing (e.g., CVE-2026-34935, CVE-2026-41497) and MCP subprocess environment variable exposure (CVE-2026-40159).
Affected software
- PraisonAI (pip package
praisonai) versions up to and including 4.6.48 - Fixed in version 4.6.59
Severity
- CVSS v3.1 Base Score: 9.8 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Upgrade PraisonAI to version 4.6.59 or later, which enforces authentication on MCP connector endpoints.
- If immediate patching is not possible:
- Do not expose the PraisonAI UI or MCP connector endpoints (
/api/mcp/connect) directly to untrusted networks or the public internet. - Bind the PraisonAI UI service to
127.0.0.1(localhost) instead of0.0.0.0, or restrict access via firewall rules/network segmentation to trusted hosts only. - Place the service behind an authenticating reverse proxy or VPN until patched.
- Monitor for unexpected outbound process spawns or unusual MCP client connections originating from PraisonAI hosts.
- Do not expose the PraisonAI UI or MCP connector endpoints (

