CVE-2026-77314
Received Received - Intake

Path Traversal in Flyto2 Core MCP Recipe Handler

Vulnerability report for CVE-2026-77314, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-19

Last updated on: 2026-11-19

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-19
Last Modified
2026-11-19
Generated
2026-11-20
AI Q&A
2026-11-19
EPSS Evaluated
N/A
NVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
flyto flyto2_core to 2.26.8 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Flyto2 Core is an automation and AI-agent workflow execution kernel. The vulnerability involves the MCP run_recipe tool accepting a recipe_name parameter that is appended to a fixed path without proper path resolution. This allows directory traversal sequences like ../ to load and execute YAML workflows from outside the intended recipe directory, bypassing security boundaries.

Detection Guidance

Check Flyto2 Core version with pip show flyto2-core or grep version in installed files. Inspect recipe execution logs for unexpected parent-directory traversal in recipe_name parameters. Monitor for unauthorized workflow executions outside the intended recipes directory.

Impact Analysis

An attacker with access to the MCP run_recipe tool could execute unintended workflows outside the designated recipe directory. While not granting full code execution, this could allow unauthorized use of allowed modules like browser, network, file, or data-processing operations, potentially leading to data leaks or unintended actions.

Compliance Impact

This vulnerability could lead to unauthorized data access or processing, violating GDPR principles like data minimization and integrity or HIPAA requirements for safeguarding protected health information. Unintended workflow execution may result in non-compliant data handling or exposure.

Mitigation Strategies

Upgrade Flyto2 Core to version 2.26.8 or later immediately. Review and restrict access to MCP run_recipe tool. Audit existing recipes for unauthorized parent-directory references. Implement input validation for recipe_name parameters to prevent path traversal.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-77314. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...