llamaCVEVulnerability Intelligence
/
Flyto Core

CVE-2026-77316

Flyto Core server-side request forgery via DNS rebinding in URL guard

An attacker who controls a domain's DNS can make outbound requests reach internal services and read the responses.

Specific setups onlyParche disponibleserver-side request forgery (SSRF)
Descargar PNG JSON
CVSS 3.1
7.1
Alta
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N Fuente: CNA
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versiónPrimer parche a -131 d de la divulgación
Exposición8 hDesde la divulgación, 19 nov 2026, 4:46 p. m.
Detección7 minDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Parche 2.26.8
Monitoreo
Detectada +2
11 jul 26
19 nov 26
20 nov 26
11 jul 26
13 ago 26
15 sept 26
18 oct 26
20 nov 26
FechaFaseEventoDetalle
Remediación Parche 2.26.8 flyto-core · -131 d desde divulgación
Divulgación Publicada CVE-2026-77316 divulgada · CVSS 7.1 (CNA)
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: NIST NVD Registro visto por primera vez en NIST NVD
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 19 nov 2026

Flyto2 Core's URL safety check can be bypassed with DNS rebinding, so an attacker who controls a hostname's DNS can make the software's outbound requests reach internal systems, including metadata services, and read the responses. An attacker with low-privilege network access can trigger this remotely, but it depends on a low DNS TTL and a timing-dependent change in DNS answers.

Only affects flyto-core 2.26.7 and earlier with an outbound HTTP module driven by an attacker-supplied URL. Fixed in 2.26.8.

¿Qué significa?The SSRF guard in validate_url_ssrf resolves a hostname, then the connection resolves it again without pinning the address. If DNS answers differently between those two lookups, requests can reach internal or metadata services the guard is meant to block, potentially including cloud metadata credentials.
¿Quién está afectado?Affected versions are flyto-core 2.26.7 and earlier, in setups with an outbound HTTP module driven by an attacker-supplied URL. To check, look at the installed flyto-core version and whether that module takes URLs from untrusted input.
¿Qué hacer?Upgrade flyto-core to 2.26.8, which is the listed fixed version.
Descripción original del registro (GitHub_M)

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.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Attacker controls DNS for the target hostname, with low or zero TTL and a flipped answer between the guard's lookup and the connection's lookup“needs attacker-controlled DNS with a low/zero TTL and to flip the answer between the guard's lookup and the connection's lookup”
02
flyto-core version 2.26.7 or earlier, with an outbound HTTP module driven by an attacker-supplied URL“all confined to v<=2.26.7”
¿Quién debe revisar?Teams running flyto-core 2.26.7 or earlier (PyPI) with outbound HTTP modules such as http.get, graphql, monitor.http_check or notification modules fed attacker-influenced URLs
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:H
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:C
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:L
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida Última
flyto-core< 2.26.8
2.26.8
2.41.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
pypiflyto-core
Corregida 2.26.8 -131 d 2.41.0 no afectada
Versiones corregidas2.26.8
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Fabricantehttps://github.com/flytohub/flyto-core/security/advisories/GHSA-6pm8-6f34-9v3g
Otrahttps://github.com/flytohub/flyto-core/commit/bf748df864d348004cf45d830bc59f62c5c4a58a
Otrahttps://github.com/flytohub/flyto-core/releases/tag/v2.26.8

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.