Flytohub flyto-core
Flyto2 Core: Unauthenticated Command Execution via HTTP MCP `execute_module`
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2.26.2, < 2.26.4
Fixed in 2.26.4
Mitigation
Upgrade flyto-core to 2.26.4 or later.
References
- Vendor advisory github.com/flytohub/flyto-core/security/adviso…
- Patch github.com/flytohub/flyto-core/commit/db7f116b…
- Release notes github.com/flytohub/flyto-core/releases/tag/v2…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.