External risk intelligence

Flyto2 Core Sandbox Escape Allows Host Code Execution

CVE advisorySeverity: CRITICAL (CVSS 10.0)

CVE-2026-77312

Flyto2 Core is an automation and AI-agent workflow execution kernel. While these kernels often run as backend services or internal processing engines, they may be integrated into internet-facing automation platforms or agentic web services. The vulnerability context involves module execution, but it does not establish that the product itself is commonly deployed as a public-facing edge or gateway service.

Path Traversal

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory describes a critical vulnerability in Flyto2 Core, an execution kernel for automation and AI-agent workflows. The issue could allow an attacker to write malicious code to sensitive system files outside of the intended sandbox, potentially leading to unauthorized code execution on the host.

  • Unrestricted file writes can bypass security controls.
  • Critical system files could be overwritten by attackers.
  • Confirm if Flyto2 Core is used in your environment.

Attack Path

How an attacker could exploit the issue

An attacker can leverage this vulnerability by triggering specific modules within Flyto2 Core, such as `data.csv.write` or `file.copy`. These modules, when improperly configured, do not enforce proper path validation, allowing an attacker to write arbitrary files outside the designated sandbox. This could lead to the overwriting of critical system files, potentially resulting in unauthorized code execution on the host system.

  • Unrestricted module execution required.
  • Trigger vulnerable file writing modules.
  • Gain host code execution.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an attacker could write arbitrary content to files outside the designated sandbox directory. This could lead to the compromise of application code, startup configurations, or system authorization files, potentially resulting in code execution on the host system.

  • Application code or configuration files.
  • Writing attacker-controlled content to host files.
  • Gaining code execution on the host.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Flyto2 Core execution kernel, used for automation and AI-agent workflows, is likely managed by platform or infrastructure teams. Initial actions should focus on identifying all instances of Flyto2 Core, assessing their exposure and criticality, and then coordinating remediation with the accountable owners.

  • Platform/Infrastructure teams own remediation.
  • Verify Flyto2 Core deployment and reachability.
  • Plan vendor engagement for patch deployment.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Flyto2 Core?

Flyto2 Core is a specialized execution kernel designed to run automation tasks and workflows for AI agents. It serves as the underlying engine that processes and executes programmed instructions, often managing how these agents interact with data, local file systems, and various reporting modules to complete their objectives.

What does CWE-22 mean for CVE-2026-77312?

This CVE involves a weakness known as Improper Limitation of a Pathname to a Restricted Directory (CWE-22). In plain English, the software fails to properly check file paths, allowing users to move outside of a designated 'sandbox' folder. Because the security controls are not applied consistently, an attacker can trick the system into writing or modifying files anywhere on the host computer.

How does an attacker trigger this vulnerability?

An attacker triggers this by executing specific modules within Flyto2 Core that handle file operations, such as moving, copying, or writing data to CSV and JSON formats. The flaw exists because these modules ignore the sandbox boundaries; simply running a task that utilizes these vulnerable modules with a manipulated destination path is sufficient to bypass security. Normal, non-module-based operations do not trigger this.

Do I need to worry if my instance is not internet-facing?

Halo Surface Signal indicates that while Flyto2 Core can be part of public-facing web services, it is frequently used as an internal processing engine. Even if your instance is not directly on the internet, any local user or integrated service with the ability to trigger these execution modules can exploit the flaw. You should prioritize internal systems that process untrusted inputs or data.

What is the first step to remediate this?

The most effective first step is to verify your installed version of Flyto2 Core and upgrade to 2.26.8 immediately. Because this vulnerability affects how the software handles files during automation, confirming your current version is necessary to ensure you are no longer relying on incomplete path validation logic. Coordinate with your platform teams to verify deployment and roll out the update.

References