PraisonAI ToolsMCPServer legacy SSE transport accepts attacker Host/Origin and exposes registered tools
CVE-2026-57112 · GHSA-vmf9-xx9w-86wx · published 2026-06-18 · updated 2026-07-20
- Severity
- High
- CVSS score
- 8.3
- Chance of exploitation (EPSS)
- 0.22%
- Fixed in
- 1.6.59
- Exploitation Public proof of concept
- Automatable No
- Technical impact Total
- CISA SSVC
If a PraisonAI user starts a local or internal legacy SSE MCP server with registered tools, an attacker who gets that user to visit a malicious website can use DNS rebinding to interact with the SSE server through the browser. The attacker can discover exposed tools and invoke them as the local user. Impact depends on the configured tools. In realistic PraisonAI MCP deployments, registered tools may access local files, repositories, issue trackers, cloud APIs, internal services, or other automation targets. This can lead to confidentiality, integrity, and availability impact for the resources reachable by the exposed tools. The PoV is local-only and harmless.
Upgrade praisonaiagents to 1.6.59 or later, and praisonai to 4.6.59 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.
Bring legacy SSE server security in line with the current Streamable HTTP transport, or disable the legacy SSE server path. Recommended changes: 1. Add explicit allowed-origin and allowed-host validation to both /sse and /messages/. 2. Reject invalid Origin with HTTP 403 before opening the SSE stream or accepting POST messages. 3. Validate Host for local and internal deployments to mitigate DNS rebinding even when browsers omit or vary Origin. 4. Require authentication for all non-stdio MCP HTTP transports, including SSE. 5. Add --api-key, --allowed-origins, and --allowed-hosts options to praisonai mcp run and praisonai serve mcp when --transport sse is used. 6.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| praisonaiagents | PyPI | >= 0.6.0, <= 1.6.58 | 1.6.59 |
| praisonai | PyPI | >= 3.10.0, <= 4.6.58 | 4.6.59 |
- 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: CodeAgent Executes LLM-Generated Code Without Sandboxing and Leaks All Environment Secretspraisonaiagents
- 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
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.