CVE-2026-77312
Flyto file-writing modules could escape the configured sandbox
flytohub · Flyto2 Core · agent workflow runtime
First documented disclosure · Review checkpoint
Summary
Several data/file modules could write attacker content outside FLYTO_SANDBOX_DIR.
Severity and exploitation evidence
Critical · 10.0/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.
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
Only selected modules used the canonical path guard; absolute paths bypassed a substring denylist.
Conditions required
A caller can run modules or recipes.
Potential impact
Host-file overwrite and possible code execution after a relevant file is used.
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
Enforce path confinement centrally across all file-writing modules.
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 10.
Sources
- GitHub_M CVE authority record
Primary source ·
- Original Flyto advisory
Primary source ·