HIGHCVSS v3.1 7.1Vulnerability

CVE-2026-77316

# [MEDIUM] SSRF guard bypass via DNS rebinding — validate_url_ssrf resolves-then-connects without pinning - **CWE:** CWE-918 (SSRF) / CWE-367 (TOCTOU). - **CVSS v3.1:** `AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N` = **6.8 Medium** (AC:H — needs attacker-controlled DNS with a low/zero TTL and to flip the answer between the guard's lookup and the connection's lookup; S:C — reaches internal/metadata services the guard is meant to block; C:H — e.g. cloud metadata credentials at 169.254.169.254). - **Affected component:** `flyto-core` (PyPI `flyto-core`), HEAD `ae2b38e` (v2.26.7). `src/core/utils.py::validate_url_ssrf` (resolution at `getaddrinfo` ~L512, `is_private_ip` check ~L515) and every consumer: `guarded_aiohttp_request()`, `enforce_outbound_url()`/`validate_url_with_env_config()` — i.e. `http.get/request/batch`, `graphql.query/mutation`, `monitor.http_check`, `notification.{slack,discord,teams}`, `ai.vision_analyze`, `verify.visual_diff`, `browser.proxy_rotate`, etc. - **Relationship:** Incomplete hardening of the SSRF-guard family (**GHSA-pgwh-4jj4-qm8v**, **GHSA-c9hr-64h3-gxpc**, **GHSA-794r-5rp2-fpg8**/CVE-2026-55787). Those fixes added per-module coverage, redirect revalidation, and IPv6-transition range-checks — but none pins the resolved address, so the guard's resolve-then-connect gap defeats all of them. ## Root cause `validate_url_ssrf()` resolves the hostname with `socket.getaddrinfo()` and rejects the URL if any resolved IP is private. It then returns the **URL string** (hostname intact). The caller (`guarded_aiohttp_request`: `validate_url_with_env_config(url)` then `session.request(method, url, ...)`) hands the hostname to aiohttp, which performs an **independent second DNS resolution** at connect time. The validated IP is never pinned for the connection, so an attacker whose authoritative DNS returns a public A record for the guard's lookup and a private/loopback/metadata address for the connection's lookup reaches internal space. aiohttp resolves via it

Properties

Severity
high
Summary
Flyto2 Core: SSRF guard bypass via DNS rebinding (validate_url_ssrf resolves-then-connects without pinning)
Nvd fetched at
2026-11-22T12:30:49.958423+00:00
Epss score
0.00347
Cvss severity
HIGH
Cvss score
7.1
Retrieved at
2026-11-22T12:32:28+00:00
Ghsa published
2026-11-20T00:11:24Z
Source url
https://github.com/advisories/GHSA-6pm8-6f34-9v3g
Ghsa updated
2026-11-20T00:11:26Z
Ghsa id
GHSA-6pm8-6f34-9v3g
Last source
FIRST EPSS
Score
7.1
Cvss version
3.1
Cve id
CVE-2026-77316
Cvss vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N
First seen by Signal
2026-11-19T23:31:53+00:00
Name
CVE-2026-77316
Is ghsa only
false
Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N

Related Entities (3)

AFFECTS (1)

→[Software]pip/flyto-core

HAS_WEAKNESS (1)

VULNERABLE_TO (1)

←[Software]pip/flyto-core

Related research

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-77316 (CVSS v3.1 7.1) — Ninja Signal Threat Intelligence | Ninja Signal