Skip to main content
Menu
CVEs

Flyto Core unauthorized workflow execution in MCP run_recipe tool

CVE-2026-77314Published November 19, 2026, updated

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.26.8
Who is exposed
Not reported

Summary

Flyto2 Core (flyto-core) contains a path traversal flaw in its MCP run_recipe tool, which lets a remote attacker who has low-privilege access run workflows stored outside the bundled recipe directory. The attacker can thereby execute allowed browser, network, file, and data-processing modules, though the module policy still limits what those workflows can do.

Written by a model

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.

What to do

Upgrade to a fixed version: 2.26.8.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-77314 (Flyto2 Core: Path traversal in MCP `run_recipe` allows execution of workflows outside bundled recipe directory), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-77314 (entry last updated 2026-11-19):
Affected:
- flytohub flyto-core: fixed in 2.26.8
Fixed versions: 2.26.8.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-77314 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77314 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/flytohub/flyto-core/security/advisories/GHSA-mxcc-cr6x-2mvr
- https://github.com/flytohub/flyto-core/commit/bbb6f1cfec22fee1ea0e6ecf1129d7103c85e09f
- https://github.com/flytohub/flyto-core/releases/tag/v2.26.8
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-77314
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77314"}.

Affected versions

cve.now Index

9Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.3/10CVSS 6.3
  • No patch0/5No signal

What would change the score

  • Would score about 64 if added to CISA KEV
  • Would score about 59 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · flytohub/flyto-core · Advisory GHSA-mxcc-cr6x-2mvr
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-77314
RecordNVD · CVE-2026-77314
Other links 2
RepositoryGitHub · flytohub/flyto-core · Commit bbb6f1cf
RepositoryGitHub · flytohub/flyto-core · Release v2.26.8

Questions about CVE-2026-77314

Is CVE-2026-77314 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-77314?

flyto-core: before 2.26.8.

Source: cve.now feed data

How do I fix CVE-2026-77314?

Upgrade to a fixed version: 2.26.8.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.