CVE-2026-57123: PraisonAI MCP SSE Transport Binds 0.0.0.0 Vulnerability
CRITICALCVE-2026-57123 is a CRITICAL (CVSS 9.8) mcp sse transport binds 0.0.0.0 vulnerability (CWE-1327: Binding to an Unrestricted IP Address) affecting PraisonAI libraries in the PyPI ecosystem. The issue involves mcp sse transport binds 0.0.0.0 with no authentication and no origin validation; bundled securityconfig is never wired in. Remediation is available by upgrading affected packages to version 1.6.59.
CVE-2026-57123 at a Glance
Security Impact
CVSS: 9.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2026-57123
To remediate this vulnerability, upgrade all affected PraisonAI dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install praisonaiagents>=1.6.59
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show praisonaiagents
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2026-57123, inspect your installed packages using pip:
pip show praisonaiagents
Analyze the terminal output to locate any version of PraisonAI in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.6.59), your application is affected.
Note: The pip show praisonaiagents command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-1327: Binding to an Unrestricted IP Address, where the product assigns the address 0.0.0.0 for a database server, a cloud service/instance, or any computing resource that communicates remotely. In PraisonAI, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-57123 Affected PraisonAI Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
praisonaiagents
|
PyPI |
< 1.6.59
|
1.6.59
|
References
Frequently Asked Questions
What is CVE-2026-57123?
Which PraisonAI versions are affected?
What version fixes CVE-2026-57123?
Is praisonaiagents affected?
What is the CVSS score of CVE-2026-57123?
What CWE is associated with CVE-2026-57123?
How can I check PyPI dependencies for CVE-2026-57123?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-x227-pf99-vffg",
"modified" : "2026-07-20T21:25:09Z",
"published" : "2026-06-18T13:55:54Z",
"aliases" : [ "CVE-2026-57123" ],
"summary" : "PraisonAI: MCP SSE transport binds 0.0.0.0 with no authentication and no Origin validation; bundled SecurityConfig is never wired in",
"details" : "The MCP SSE server started via ToolsMCPServer.run_sse() / launch_tools_mcp_server(transport=\"sse\")\nbinds to 0.0.0.0 by default and builds its Starlette application with no authentication middleware\nand no Origin-header validation. The module mcp/mcp_security.py provides exactly the needed controls\n(origin validation, DNS-rebinding detection, auth-header enforcement, a SecurityConfig), but none of\nthese functions are ever called by any transport — they are dead code. Any host that can reach the\nport can list and invoke every registered tool with no credentials, and a victim's browser can drive\nthe same calls against a localhost instance via DNS rebinding.\n\nAffected code: src/praisonai-agents/praisonaiagents/mcp/mcp_server.py\n- run_sse defaults host to all interfaces (line 245) and builds the app with only `debug` and `routes`\n - no `middleware=` and no per-route auth/origin gate (lines ~271-289):\n app = Starlette(debug=self._debug, routes=[\n Route(sse_path, endpoint=handle_sse), # \"/sse\"\n Mount(messages_path, app=sse_transport.handle_post_message), # \"/messages/\"\n ])\n uvicorn.run(app, host=host, port=port)\n- launch_tools_mcp_server also defaults host=\"0.0.0.0\" (line 301).\n\nsrc/praisonai-agents/praisonaiagents/mcp/mcp_security.py defines but the transports never call:\n- is_valid_origin (line 30), is_potential_dns_rebinding (line 110), validate_auth_header (line 167),\n SecurityConfig.is_origin_allowed (line 236). These symbols are referenced only inside mcp_security.py\n and the __init__ re-export. (mcp_websocket.py's auth references are CLIENT-side, not server validation.)\n\nImpact:\nlaunch_tools_mcp_server(transport=\"sse\") is the documented path for exposing tools over MCP. With the\ndefaults above it is an unauthenticated, network-reachable tool-execution endpoint. Blast radius equals\nthe capabilities of the registered tools; with file/shell/code-exec tools this is RCE. With no Origin\ncheck, a malicious page the victim merely visits can rebind its hostname to 127.0.0.1 and issue the\nJSON-RPC calls cross-origin against a developer's local server.\n\nProof of concept:\nStatic proof (AST analysis of unmodified source):\n Check 1 - run_sse(host='0.0.0.0'); launch_tools_mcp_server(host='0.0.0.0') -> EXPOSED\n Check 2 - Starlette(...) kwargs: ['debug','routes'] -> NO middleware= (no auth/origin gate)\n Check 3 - is_valid_origin / is_potential_dns_rebinding / validate_auth_header / SecurityConfig\n never called by any transport -> DEAD CODE\nLive exploitation against a running server:\n curl -N http://VICTIM:8080/sse\n # event: endpoint / data: /messages/?session_id=<sid>\n curl -X POST \"http://VICTIM:8080/messages/?session_id=<sid>\" -H 'Content-Type: application/json' \\\n -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2024-11-05\",\n \"capabilities\":{},\"clientInfo\":{\"name\":\"x\",\"version\":\"1\"}}}'\n curl -X POST \"http://VICTIM:8080/messages/?session_id=<sid>\" -H 'Content-Type: application/json' \\\n -d '{\"jsonrpc\":\"2.0\",\"id\":2,\"method\":\"tools/call\",\"params\":{\"name\":\"<tool>\",\"arguments\":{...}}}'\nNo Authorization header anywhere. Browser DNS-rebinding variant drives the same calls cross-origin.\n\nRemediation:\nWire in the existing mcp_security.py controls and fix defaults:\n- Default run_sse(host=\"127.0.0.1\"); require explicit opt-in to bind 0.0.0.0.\n- Attach Starlette middleware calling is_valid_origin / is_potential_dns_rebinding; reject bad origins.\n- Enforce validate_auth_header when SecurityConfig.require_auth; default require_auth=True (and\n allow_missing_origin=False) for any non-loopback bind.\n\nDistinct from prior advisories:\nThe accepted MCP advisories are tool-handler bugs — tools/call path traversal -> .pth RCE\n(GHSA-9mqq-jqxf-grvw) and unauthenticated file read via workflow.show/validate (GHSA-9cr9-25q5-8prj).\nThis is a transport-layer missing-auth/exposure: the SSE server never enforces auth or Origin validation\nand ignores the security module the codebase ships. Closest in spirit to the default-insecure pattern\n(GHSA-8444 / 86qc) but a different server and a different root cause (unwired controls, not an unset env var).",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "praisonaiagents"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.6.59"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-x227-pf99-vffg"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/MervinPraison/PraisonAI"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-1327", "CWE-306", "CWE-350" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-18T13:55:54Z",
"nvd_published_at" : null
}
}