Multiple security vulnerabilities have been identified in Flyto2 Core, affecting its module execution, file-writing, and outbound HTTP request handling. The flaws span the recipe and module execution surface, filesystem write operations, and outbound URL validation in affected releases up to 2.26.7. A remote attacker with module access or DNS control can bypass sandbox and SSRF protections, read internal data, and in some cases overwrite files to gain code execution.
CVE-2026-77312: This path-traversal flaw affects file-writing functionality that lacks sandbox confinement, allowing a client able to invoke modules to write attacker-controlled content to arbitrary absolute paths. Overwriting application code, recipes, or configuration files can lead to code execution.[/subscribe_to_unlock_form]
Multiple security vulnerabilities have been identified in Flyto2 Core, affecting its module execution, file-writing, and outbound HTTP request handling. The flaws span the recipe and module execution surface, filesystem write operations, and outbound URL validation in affected releases up to 2.26.7. A remote attacker with module access or DNS control can bypass sandbox and SSRF protections, read internal data, and in some cases overwrite files to gain code execution.
CVE-2026-77312: This path-traversal flaw affects file-writing functionality that lacks sandbox confinement, allowing a client able to invoke modules to write attacker-controlled content to arbitrary absolute paths. Overwriting application code, recipes, or configuration files can lead to code execution.[emaillocker id="1283"]
CVE-2026-67429 (CVSS 10.0 — Critical): This critical path-traversal vulnerability in Flyto2 Core's file-writing modules allowed an attacker who could invoke modules to write arbitrary content to arbitrary filesystem locations. The flaw can enable overwriting application code or configuration to achieve code execution.
CVE-2026-55786: This issue affects the HTTP module execution surface and permits unauthenticated access to module invocation. It increases the reachability of the surrounding file-write and SSRF flaws by allowing remote clients to trigger vulnerable modules without prior authentication.
CVE-2026-77313 (CVSS 7.1 — High): The SSRF guard validates a resolved address but then allows the connection to use a separate DNS lookup without pinning the validated address. An attacker controlling DNS can return a public address during validation and an internal address during connection, causing guarded requests to reach internal services.
CVE-2026-77315 (CVSS 8.5 — High): The pagination feature validates only the initial request target and follows server-supplied next-page references without revalidating them. A malicious first response can direct subsequent requests to internal addresses, causing a second-order SSRF whose internal response is returned to the caller.
CVE-2026-77316 (CVSS 7.1 — High): The SSRF guard's resolve-then-connect design does not pin the validated address, so an attacker with DNS control can cause the guard to see a public address while the outbound connection resolves to a private or metadata address. This bypasses the guard across guarded HTTP and related outbound request paths.
CVE-2026-55787: This SSRF-guard issue in Flyto2 Core's outbound URL handling allowed server-controlled requests to reach internal addresses. It is part of the same outbound request validation weakness that can be bypassed when the validated address is not pinned for the connection.
These vulnerabilities collectively present a severe risk to deployments that expose module execution or outbound request functionality to untrusted users. The greatest exposure is for environments where remote clients can invoke modules or where DNS-controlled hosts are used for outbound requests. They should be treated as high priority to prevent sandbox escape, internal data disclosure, and code execution.
The following reports contain further technical details:
[/emaillocker]