CVE-2026-77314

published 19 Nov 2026 · updated 20 Nov 2026

Flyto2 Core: Path traversal in MCP `run_recipe` allows execution of workflows outside bundled recipe directory

6.3MediumCVSS 6.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
flytohub<2.26.8

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-77314 severity on Zeptric[![CVE-2026-77314](https://zeptric.io/badge/cve/CVE-2026-77314.svg)](https://zeptric.io/cve/CVE-2026-77314)