Vulnerability details

Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.3, validate_url_ssrf and is_private_ip in src/core/utils.py compare resolved addresses only against native private IPv4 and IPv6 ranges and do not unwrap IPv4-mapped, IPv4-compatible, 6to4, or NAT64 transition addresses. An authenticated workflow author can provide a transition-form literal URL through the Execution API POST /v1/execute route, http.get, or sibling guarded outbound-request modules, causing the guard to accept an address whose embedded IPv4 points to loopback, RFC 1918, or cloud metadata services. On a host that routes the selected transition form, the outbound request reaches the internal destination and returns the response body to the workflow caller, enabling read SSRF and disclosure of internal-service data or cloud credentials. This issue is fixed in version 2.26.3.

• https://github.com/flytohub/flyto-core/pull/20 x_refsource_MISC
• https://github.com/flytohub/flyto-core/commit/519e040384a74984848c4e84a6600e5f1020a6d2 x_refsource_MISC
• https://github.com/flytohub/flyto-core/releases/tag/v2.26.3 x_refsource_MISC
• https://github.com/flytohub/flyto-core/security/advisories/GHSA-794r-5rp2-fpg8 x_refsource_CONFIRM