UTC
High

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

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.

What to do

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.

Affected
PackageRegistryAffectedFixed in
praisonaiagentsPyPI>= 0.6.0, <= 1.6.581.6.59
praisonaiPyPI>= 3.10.0, <= 4.6.584.6.59

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].