CVE-2026-57139: PraisonAI: unauthenticated MCP server exposes agent tools
CRITICALPoC AVAILABLECISA: ATTENDPraisonAI's TypeScript MCPServer.startHttp() (versions 1.5.0 through 1.7.2) listens without a host restriction and passes every HTTP POST to its request handler with no authentication or authorization. Anyone who can reach the port can list and call registered tools and read resources and prompts, which run with the server's credentials and process privileges. This is a CVSS 9.8 flaw, but real-world urgency is moderate for now: EPSS is 0.75% (46th percentile), it is not in CISA KEV, and there is no public exploit or Nuclei template, although CISA SSVC rates it ATTEND. Exposure depends on whether the MCP server is reachable beyond localhost, so inventory any PraisonAI TypeScript deployments that use MCPServer, upgrade past the initial fix in 1.7.2 (the advisory notes that remediation was only an initial one, so check GHSA-j4f3-55x4-r6q2 for the final fixed release), and firewall or authenticate the port until you have done so.
What is the risk?
Critical severity (CVSS 9.8) with network attack vector, low complexity, no privileges and no user interaction. Exploitation is trivial for anyone who can reach the port: a single unauthenticated HTTP POST can invoke tools. Current exploitation likelihood is modest (EPSS 0.00754, top 46%, not in KEV, no public exploit or scanner template). Actual impact depends on which tools, secrets and data sources are registered on the server. Because the default bind is unrestricted, servers on shared networks, cloud VMs or containers with published ports are at the highest risk. The advisory describes the 1.7.2 fix as an initial remediation, so residual risk may remain in that version.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| PraisonAI | pip | — | No patch |
Do you use PraisonAI? You're affected.
How severe is it?
What is the attack surface?
What should I do?
1 step1) Upgrade PraisonAI TypeScript to a release newer than 1.7.2 once the full fix is available, and review the GHSA-j4f3-55x4-r6q2 advisory and the referenced commit 709a038 for the final fixed version. 2) Until patched, bind the MCP server to 127.0.0.1 only, or place it behind a reverse proxy or API gateway that enforces authentication (mTLS, bearer tokens) and IP allow-lists. 3) Block the MCP port at the host and network firewall and in container or security-group rules. 4) Reduce the privileges and credentials available to registered tool handlers (least privilege, scoped short-lived tokens) and remove high-risk tools such as shell, file-write or database-admin tools from exposed servers. 5) Detection: search web and proxy logs for unexpected POSTs to the MCP endpoint, especially JSON-RPC methods tools/list, tools/call, resources/read and prompts/get from unknown source IPs; scan internal ranges for the open port; rotate any secrets that were reachable by the server if exposure is suspected.
What does CISA's SSVC say?
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-57139?
PraisonAI's TypeScript MCPServer.startHttp() (versions 1.5.0 through 1.7.2) listens without a host restriction and passes every HTTP POST to its request handler with no authentication or authorization. Anyone who can reach the port can list and call registered tools and read resources and prompts, which run with the server's credentials and process privileges. This is a CVSS 9.8 flaw, but real-world urgency is moderate for now: EPSS is 0.75% (46th percentile), it is not in CISA KEV, and there is no public exploit or Nuclei template, although CISA SSVC rates it ATTEND. Exposure depends on whether the MCP server is reachable beyond localhost, so inventory any PraisonAI TypeScript deployments that use MCPServer, upgrade past the initial fix in 1.7.2 (the advisory notes that remediation was only an initial one, so check GHSA-j4f3-55x4-r6q2 for the final fixed release), and firewall or authenticate the port until you have done so.
Is CVE-2026-57139 actively exploited?
Proof-of-concept exploit code is publicly available for CVE-2026-57139, increasing the risk of exploitation.
How to fix CVE-2026-57139?
1) Upgrade PraisonAI TypeScript to a release newer than 1.7.2 once the full fix is available, and review the GHSA-j4f3-55x4-r6q2 advisory and the referenced commit 709a038 for the final fixed version. 2) Until patched, bind the MCP server to 127.0.0.1 only, or place it behind a reverse proxy or API gateway that enforces authentication (mTLS, bearer tokens) and IP allow-lists. 3) Block the MCP port at the host and network firewall and in container or security-group rules. 4) Reduce the privileges and credentials available to registered tool handlers (least privilege, scoped short-lived tokens) and remove high-risk tools such as shell, file-write or database-admin tools from exposed servers. 5) Detection: search web and proxy logs for unexpected POSTs to the MCP endpoint, especially JSON-RPC methods tools/list, tools/call, resources/read and prompts/get from unknown source IPs; scan internal ranges for the open port; rotate any secrets that were reachable by the server if exposure is suspected.
What systems are affected by CVE-2026-57139?
This vulnerability affects the following AI/ML architecture patterns: agent frameworks, MCP servers, multi-agent systems, tool-calling pipelines.
What is the CVSS score for CVE-2026-57139?
CVE-2026-57139 has a CVSS v3.1 base score of 9.8 (CRITICAL). The EPSS exploitation probability is 0.75%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0049Exploit Public-Facing ApplicationAML.T0053AI Agent Tool InvocationAML.T0084.001Tool DefinitionsAML.T0085.001AI Agent ToolsAML.T0098AI Agent Tool Credential HarvestingCompliance Controls Affected
What are the technical details?
Original Advisory
PraisonAI is a multi-agent teams system. From 1.5.0 until 1.7.2, MCPServer.startHttp() in src/praisonai-ts/src/mcp/server.ts binds without a host restriction and forwards every HTTP POST request to handleRequest() without authentication or authorization. Any network client that can reach the port can call tools/list, tools/call, resources/read, or prompts/get, causing registered handlers to run with server-side credentials and process privileges or disclose registered data. An initial remediation was released in version 1.7.2.
Exploitation Scenario
An attacker scans for hosts running a PraisonAI MCP server, or finds one on an internal network after an initial foothold. They send an unauthenticated JSON-RPC POST with tools/list to enumerate the registered tools, then call tools/call to run tools such as a database query, file reader or internal API client. They also call resources/read and prompts/get to pull registered data and system prompts. Because the handlers use the server's credentials, the attacker uses them to exfiltrate data, take actions in connected SaaS or cloud systems, or move laterally, without ever interacting with the LLM.
Weaknesses (CWE)
CWE-1188Initialization of a Resource with an Insecure DefaultPrimaryCWE-306Missing Authentication for Critical FunctionalityPrimaryCWE-862Missing AuthorizationPrimaryCWE-1188Initialization of a Resource with an Insecure DefaultCWE-306Missing Authentication for Critical FunctionalityCWE-862Missing AuthorizationCWE-1188 — Initialization of a Resource with an Insecure Default: The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HReferences
Timeline
Related Vulnerabilities
CVE-2026-4816810.0PraisonAI: shell injection in Claude Action enables RCE
Same package: praisonaiCVE-2026-6144710.0PraisonAI: RCE via unsandboxed LLM code execution
Same package: praisonaiCVE-2026-614459.9PraisonAI: AICoder root RCE via unsanitized tool calls
Same package: praisonaiGHSA-vmmj-pfw7-fjwp9.9praisonai: sandbox escape gives RCE via codeMode tool
Same package: praisonaiCVE-2026-473929.9praisonaiagents: RCE via Python sandbox bypass
Same package: praisonai