{"answers":{"affected":"3 open source packages ship an affected version, including flyto-core.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67425 exists.","fix":"Upgrade flyto-core to 2.26.7 or later.","what":"CVE-2026-67425 is a high-severity vulnerability in flytohub flyto-core, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-67425 and fix it if it is affected.\n\nWhat it is: CVE-2026-67425 is a high-severity vulnerability in flytohub flyto-core, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67425 exists.\n\nAffected packages and fixed versions:\n- flyto-core (PyPI): affected all versions; fixed in 2.26.7\n- flyto-core (PyPI): affected all versions; fixed in 2.26.7\n- flyto-core (PyPI): affected all versions; fixed in 2.26.7\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-67425/ (Markdown: https://insights.sbomify.com/CVE-2026-67425/index.md)","id":"CVE-2026-67425","markdown":"https://insights.sbomify.com/CVE-2026-67425/index.md","name":"CVE-2026-67425","record":{"aliases":["GHSA-qq9q-xgm3-xv9g","PYSEC-2026-3573"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"AI automation library","requires_auth":"none","summary":"Attackers can steal API keys by manipulating the base_url parameter in Flyto2 Core, exposing sensitive credentials to external hosts.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-201","name":"Insertion of Sensitive Information Into Sent Data"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Flyto2 Core: LLM/API keys leak to an attacker-controlled base_url","id":"CVE-2026-67425","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Flyto2 Core: Unauthenticated flyto-verification /run: callback_url SSRF and internal runner-secret exfiltration","id":"CVE-2026-67426"},"packages":[{"ecosystem":"PyPI","fixed":["2.26.7"],"introduced":["0"],"last_affected":[],"package":"flyto-core","purl":null,"source":"GHSA-qq9q-xgm3-xv9g"},{"ecosystem":"PyPI","fixed":["2.26.7"],"introduced":["0"],"last_affected":[],"package":"flyto-core","purl":"pkg:pypi/flyto-core","source":"GHSA-qq9q-xgm3-xv9g"},{"ecosystem":"PyPI","fixed":["2.26.7"],"introduced":["0"],"last_affected":[],"package":"flyto-core","purl":"pkg:pypi/flyto-core","source":"PYSEC-2026-3573"}],"prev":{"headline":"Flyto2 Core: Guarded HTTP modules follow redirects into internal space without per-hop SSRF revalidation","id":"CVE-2026-67424"},"products":["flyto-core"],"published":"2026-07-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-29","vendors":["flytohub"]},"summary":"Attackers can steal API keys by manipulating the base_url parameter in Flyto2 Core, exposing sensitive credentials to external hosts.","url":"https://insights.sbomify.com/CVE-2026-67425/"}