Flyto2 Core - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/flyto2-core/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioThu, 13 Aug 2026 22:08:06 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgFlyto2 Core SSRF Vulnerability (CVE-2026-73530)https://feed.craftedsignal.io/briefs/2026-08-flyto2-ssrf/Thu, 13 Aug 2026 22:08:06 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-08-flyto2-ssrf/Flyto2 Core versions prior to 2.28.0 are susceptible to SSRF via an IPv6 loopback bypass in the is_private_ip() function, enabling access to internal services.Flyto2 Core before version 2.28.0 contains a Server-Side Request Forgery (SSRF) vulnerability that allows unauthorized access to internal network services. The vulnerability originates in the is_private_ip() function, which fails to correctly sanitize or block the IPv6 loopback address notation ::. Because the kernel interprets :: identically to 0.0.0.0 (loopback), attackers can circumvent existing private IP range filters and hostname validation checks. This flaw affects multiple modules, specifically http.get, http.request, and http.batch. By manipulating these functions to target ::, an attacker can force the application to make HTTP requests to internal services bound to the IPv6 loopback interface, potentially leading to unauthorized data exfiltration or service interaction. Organizations running Flyto2 Core must prioritize upgrading to version 2.28.0 or later.

Impact

Successful exploitation allows remote, unauthenticated attackers to interact with internal services that are otherwise protected by IP filtering or hostname validation, potentially leading to the leakage of internal application states, configuration data, or other sensitive information reachable via the loopback interface.

Recommendation

  • Upgrade all instances of Flyto2 Core to version 2.28.0 or later immediately to patch the is_private_ip() filter logic.
  • Review web application logs for HTTP request patterns utilizing :: or IPv6 loopback notations within URL parameters handled by the http modules.
  • Implement outbound network egress filtering at the host level to prevent the web application process from making unnecessary requests to local loopback addresses if not required by business logic.
]]>highadvisory