Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-57124 – Unauthenticated Remote Command Execution – PraisonAI ≤ 4.6.48

Be the first to know when new zero-days emerge:

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/connect endpoint that accepts attacker-supplied command and args parameters. These values are passed directly into the StdioMCPClient, which spawns a local process using the supplied command, without sanitization or authentication.
  • Trigger conditions: The service binds to 0.0.0.0 by default when started via praisonai ui, praisonai ui agents, praisonai claw, or any application built with praisonai.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 of 0.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.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge