Flyto2 Core: Unauthenticated Command Execution via HTTP MCP `execute_module`
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in flyto-core 2.26.4.
Flyto2 Core is an execution kernel for automation and AI-agent workflows. From 2.26.2 until 2.26.4, the HTTP MCP POST /mcp route accepts unauthenticated JSON-RPC tools/call requests and forwards execute_module arguments to the module registry without the require_auth dependency used by the REST execution routes. An unauthenticated caller can select sandbox.execute_shell and supply its command parameter, which reaches asyncio.create_subprocess_shell with the privileges of the flyto-core server process. The endpoint is reachable locally under the default loopback binding and becomes network reachable when an operator binds the server to a non-loopback interface, allowing arbitrary OS command execution and potential full host compromise. This issue is fixed in version 2.26.4.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| flytohub | >=2.26.2 <2.26.4 | ||
| pypi: flyto-core | >=2.26.2 <2.26.4 | 2.26.4 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in flyto-core (PyPI), strongest first
Embed
A live severity badge for an advisory, README or ticket