Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-2956-977x-2w3r

Flyto2 Core: Arbitrary file write via image.download (and other file-writing modules)

CVSS 10.0 CriticalCriticalEPSS 0.0057 · 48th percentile

Critical, because:

  • CVSS score 10.0: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 30 Jul 2026, 14:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
flyto-corePyPI<2.26.72.26.7
Identifiers
GHSA-2956-977x-2w3r · CVE-2026-67429 · PYSEC-2026-3568
Weakness (CWE)
CWE-22 · CWE-73
Tags
Published
30 Jul 2026
Updated
4 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Flyto-core versions before 2.26.7 let callers write files outside the intended sandbox. The image.download module takes a caller-supplied output_dir as its own base for the path check, so an attacker who can call it (for example through an AI agent or a remote API client) can write attacker-supplied HTTP response content to any absolute path the process can write, which can lead to code execution. Upgrade to flyto-core 2.26.7 or later; the source gives no workaround.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
10.0 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0057, the 48th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:41 UTC First seen by agentprime
  2. 31 Oct 2026, 14:41 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.