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.
References
Configurations
No configuration.
History
15 Oct 2026, 15:17
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/flytohub/flyto-core/security/advisories/GHSA-794r-5rp2-fpg8 - |
14 Oct 2026, 19:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-14 19:17
Updated : 2026-10-16 20:04
NVD link : CVE-2026-55787
Mitre link : CVE-2026-55787
CVE.ORG link : CVE-2026-55787
JSON object : View
Products Affected
No product.
CWE
CWE-918
Server-Side Request Forgery (SSRF)
