Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of flyto-core before 2.26.7 can send the operator's LLM provider key, read from the environment, to a caller-supplied base_url. An attacker who can influence base_url, such as through the MCP agent surface or the hosted API, can point it at their own public server and capture the key, which could then be used to bill or access the operator's accounts. Upgrade to flyto-core 2.26.7 or later; the source does not list a workaround other than limiting who can set base_url.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.6 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0041, the 35th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:41 UTC First seen by agentprime
- 31 Oct 2026, 14:41 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-qq9q-xgm3-xv9g
- OSV: GHSA-qq9q-xgm3-xv9g
- github.com/flytohub/flyto-core/security/advisories/GHSA-qq9q-xgm3-xv9g
- nvd.nist.gov/vuln/detail/CVE-2026-67425
- github.com/flytohub/flyto-core/commit/d5f89d71303e3c1e6418d347c5c55fcd173cc8cc
- github.com/flytohub/flyto-core
- github.com/flytohub/flyto-core/releases/tag/v2.26.6