CVE-2026-67425: flytohub flyto-core · Insertion of Sensitive Information Into Sent Data
Affects flytohub flyto-coreSource CVE Database V5
Not known to be exploited · CVSS 8.6 High : upgrade to 2.26.6 soon.
Data as of 28 Oct 2026, 05:11 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% 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:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| flytohubflyto-core | Affected
| Fixed in
|
GitHubflytohub/flyto-corepkg:github/flytohub/flyto-coreOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in flyto-core version 2.26.6. Users should upgrade to version 2.26.6 or later to remediate this issue. Since no official remediation level or patch link is provided beyond this version information, confirm with the vendor advisory for the latest patch status. Until upgraded, avoid using untrusted input for the base_url parameter or restrict network access to trusted hosts to reduce exposure.
Description
Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.6, llm.chat reads provider keys such as OPENAI_API_KEY and ANTHROPIC_API_KEY from the environment and sends them in the Authorization: Bearer header to caller-controlled base_url, allowing an attacker to receive the operator's key on a public host that passes the SSRF guard. This issue is fixed in version 2.26.6.