CVE-2026-77316
Received Received - Intake

SSRF Bypass in Flyto2 Core via DNS Race Condition

Vulnerability report for CVE-2026-77316, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-19

Last updated on: 2026-11-19

Assigner: GitHub, Inc.

Description

Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, validate_url_ssrf() in src/core/utils.py validates one DNS answer and then returns the hostname, while guarded_aiohttp_request(), enforce_outbound_url(), and validate_url_with_env_config() allow the outbound connection to perform an independent second lookup. A caller with control of the hostname's DNS can make validation see a public address and make the connection see an internal address, bypassing the guard across its outbound consumers and exposing readable internal or metadata-service responses. The attack requires low or zero DNS TTL behavior and a successful timing-dependent answer change; static multiple-address answers are checked and do not provide the same bypass. This issue is fixed in version 2.26.8.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-19
Last Modified
2026-11-19
Generated
2026-11-20
AI Q&A
2026-11-19
EPSS Evaluated
N/A
NVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
flyto2 core 2.26.8

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Flyto2 Core before 2.26.8 has a Server-Side Request Forgery (SSRF) vulnerability in its URL validation. The validate_url_ssrf() function checks one DNS response for a hostname but allows outbound connections to perform a second independent DNS lookup. An attacker controlling the hostname's DNS can make the validation see a public address while the connection sees an internal address, bypassing security controls.

Detection Guidance

This vulnerability involves DNS-based SSRF bypass due to independent DNS lookups during validation and connection. Detect it by monitoring DNS queries for unexpected internal hostnames or timing-dependent address changes. Check application logs for outbound connections to internal IPs after hostname validation. Use tools like tcpdump or Wireshark to inspect DNS and HTTP traffic for anomalies.

Impact Analysis

This vulnerability allows attackers to access internal services or metadata services that should be restricted. It requires low DNS TTL and precise timing to succeed, but could expose sensitive internal data or metadata responses if exploited.

Mitigation Strategies

Upgrade Flyto2 Core to version 2.26.8 or later to address the issue. If upgrading is not immediately possible, restrict outbound connections to trusted networks and implement DNS TTL enforcement to prevent timing-dependent attacks. Review and harden DNS configurations to avoid low-TTL behavior.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-77316. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...