Flyto2 Core: Path traversal in MCP `run_recipe` allows execution of workflows outside bundled recipe directory
flytohub flyto-core
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| flytohub flyto-core |
| No fix yet |
Original description
Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, the MCP run_recipe tool in src/core/mcp_handler.py accepts a caller-controlled recipe_name that load_recipe() in src/cli/recipe.py appends to the src/recipes path without resolved-path containment. Parent-directory segments can therefore make Flyto load and execute a YAML workflow outside the bundled recipe directory, bypassing the boundary represented by list_recipes(). This does not necessarily provide unrestricted code execution because available workflow modules remain subject to Flyto's module policy, but it permits unintended execution of allowed browser, network, file, and data-processing modules. This issue is fixed in version 2.26.8.
From the CVE record · GitHub_M