nday
CVE-2026-77316 GHSA-6pm8-6f34-9v3g

Flyto2 Core: SSRF guard bypass via DNS rebinding (validate_url_ssrf resolves-then-connects without pinning)

flytohub / flyto-core

A public PoC appeared 2 days after disclosure. Patched: fixed in flyto-core 2.26.8. Listed by 1 of 4 PoC sources: github. Not in CISA KEV.

tags weakness typeSSRF accessnetworkno user interaction ecosystemPyPI
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

SSRF
CWE-918, stated by the CNA GitHub_M, NVD, republishing [email protected], and GitHub advisory GHSA-6pm8-6f34-9v3g
network
AV:N in CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N (CVSS 3.1) from the CNA GitHub_M
no user interaction
UI:N in CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N (CVSS 3.1) from the CNA GitHub_M
PyPI
GHSA-6pm8-6f34-9v3g: pip packages flyto-core
stage
POC
disclosed
disclosure → PoC
T+2d POC is date-only
cvss
7.1 HIGH v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
11-19T21:46Z
PATpatch
11-20T01:04Z
ANAanalysis
no record yet
POCPoC
11-21, date only
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:H
High: success depends on conditions outside the attacker's control, such as gathering details of the target or winning a race
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N

CVSS 3.1 vector from the CVE record, scored by the CNA GitHub_M.

Event log

+DISdisclosed

CVE record published by GitHub_M. CVSS 7.1, high.

src cvelist · nday , observed live · raw
{
  "id": 489763,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-77316",
  "occurred_at": "2026-11-19T21:46:58.995Z",
  "observed_at": "2026-11-19T23:02:30.446371Z",
  "is_backfill": false,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N",
      "version": "3.1",
      "base_score": 7.1,
      "base_severity": "HIGH"
    },
    "state": "PUBLISHED",
    "date_published": "2026-11-19T21:46:58.995Z",
    "assigner_short_name": "GitHub_M"
  }
}
no source time; observed live by nday
+PATpatch released

The advisory gives fixed version flyto-core 2.26.8. Fix commits are linked. Advisory published ; the patch's own release time is not recorded.

src ghsa GHSA-6pm8-6f34-9v3g · nday , observed live · raw
{
  "id": 492297,
  "type": "patch_released",
  "source": "ghsa",
  "url": "https://github.com/advisories/GHSA-6pm8-6f34-9v3g",
  "occurred_at": null,
  "observed_at": "2026-11-20T01:04:39.062031Z",
  "is_backfill": false,
  "dedupe_key": "GHSA-6pm8-6f34-9v3g",
  "detail": {
    "cvss": {
      "cvss_v3": {
        "score": 7.1,
        "vector_string": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N"
      },
      "cvss_v4": {
        "score": 0.0,
        "vector_string": null
      }
    },
    "cwes": [
      {
        "name": "Server-Side Request Forgery",
        "cwe_id": "CWE-918"
      }
    ],
    "ghsa_id": "GHSA-6pm8-6f34-9v3g",
    "packages": [
      {
        "name": "flyto-core",
        "ecosystem": "pip",
        "first_patched_version": "2.26.8",
        "vulnerable_version_range": "<= 2.26.7"
      }
    ],
    "severity": "high",
    "references": [
      "https://github.com/flytohub/flyto-core/security/advisories/GHSA-6pm8-6f34-9v3g",
      "https://github.com/flytohub/flyto-core/commit/bf748df864d348004cf45d830bc59f62c5c4a58a",
      "https://github.com/flytohub/flyto-core/releases/tag/v2.26.8",
      "https://github.com/advisories/GHSA-6pm8-6f34-9v3g"
    ],
    "fix_commit_urls": [
      "https://github.com/flytohub/flyto-core/commit/bf748df864d348004cf45d830bc59f62c5c4a58a"
    ],
    "github_reviewed_at": "2026-11-20T00:11:24Z",
    "advisory_updated_at": "2026-11-20T00:11:26Z",
    "source_code_location": "https://github.com/flytohub/flyto-core",
    "advisory_published_at": "2026-11-20T00:11:24Z"
  }
}
2026-11-21date only, from source
+POCpublic PoC

PoC repository on GitHub: googlesky/CVE-2026-77316. The date is the repository's creation day.

src github 1466320878 · nday , observed live · raw
{
  "id": 498648,
  "type": "poc_published",
  "source": "github",
  "url": "https://github.com/googlesky/CVE-2026-77316",
  "occurred_at": "2026-11-21T08:02:00Z",
  "observed_at": "2026-11-21T00:00:00Z",
  "is_backfill": false,
  "dedupe_key": "1466320878",
  "detail": {
    "url": "https://github.com/googlesky/CVE-2026-77316",
    "title": "googlesky/CVE-2026-77316",
    "precision": "day"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.