CVE-2026-77314

Flyto MCP recipe names could escape the bundled recipe directory

flytohub · Flyto2 Core · agent workflow runtime

First documented disclosure · Review checkpoint

Summary

A caller could execute a YAML workflow outside the recipe list.

Severity and exploitation evidence

Medium · 6.3/10 · CVSS 3.1. Severity source.

Exploitation not established: Reviewed public sources describe the weakness, a correction or a controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The loader joins an untrusted recipe name without resolved-path containment.

Conditions required

MCP run_recipe access and a readable external YAML workflow on the server.

Potential impact

Unintended execution of allowed workflow modules; module policy still applies.

Affected versions and configurations

Before 2.26.8.

Fix and mitigation status

2.26.8.

Practical next steps

Upgrade to 2.26.8 and verify the applicable path or outbound-network controls.

Operating lesson

Constrain recipe lookup independently of module execution policy.

Evidence and limits

Original July 11 advisory predates November 19 CNA ingestion. Reviewed correction and 2.26.8 tagged utilities establish the guarded resolver; public demonstrations are not malicious exploitation. CNA publication is 2026-11-19; this is distinct from the earliest reviewed public source and correction dates. GitHub_M assessments: CVSS 3.1 6.3.

Sources