Flyto2 Core allows callers to set the destination directory for image.download and related file‑writing modules without applying sandbox path validation that uses FLYTO_SANDBOX_DIR. This absence of a check permits an attacker to supply a crafted response that is written to any file system path the process can access, potentially overwriting critical files or injecting malicious data. The problem is a classic example of Path Traversal (CWE‑22) and the improper use of input for relocation (CWE‑73).

The product is Flyto2 Core from flytohub. All releases prior to version 2.26.6 are affected. The issue is fixed in v2.26.6, which restores sandbox path validation for image.download and related modules.

With a CVSS score of 10 the vulnerability is considered critical. The EPSS score is below 1 % but still indicates that exploitation is possible, though not widespread. It is not listed in CISA’s KEV catalog. An attacker would need to invoke image.download (or a related function) with a response that writes data, which can be done remotely within an automation or AI‑agent workflow or locally if privileged. The lack of path validation allows writing to arbitrary locations, enabling data tampering or infection with malicious files. Management of the process’s file‑system permissions and sandboxing can mitigate the risk if a patch is not immediately applied.