Skip to main content
VulnerabilityPublished

CVE-2026-67429: flytohub flyto-core · Path Traversal

Affects flytohub flyto-coreSource CVE Database V5

0

Not known to be exploited · CVSS 10.0 Critical : upgrade to 2.26.6 as a priority.

Data as of 27 Oct 2026, 17:11 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.26.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade flyto-core and flytohub/flyto-core to 2.26.6.

Affected software

ProductAffectedFixed in
flytohubflyto-coreAffected
  • <2.26.6
Fixed in
  • 2.26.6
GitHubflytohub/flyto-corepkg:github/flytohub/flyto-coreOther threatsAffected
  • <2.26.6
Fixed in
  • 2.26.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade flyto-core to version 2.26.6 or later, where this vulnerability is fixed. No other official remediation or temporary fixes are indicated. Patch status is confirmed by the vendor advisory stating the fix is in 2.26.6.

Description

Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.6, image.download and related file-writing modules use caller-controlled output_dir instead of validate_path_with_env_config and its FLYTO_SANDBOX_DIR confinement, allowing attacker-controlled response bytes to be written to arbitrary filesystem paths the process can access. This issue is fixed in version 2.26.6.

References

Community reviews

Loading reviews…