{"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-67426 exists.","fix":"Upgrade flyto-core to 2.26.7 or later.","what":"CVE-2026-67426 is a critical server-side request forgery 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-67426 and fix it if it is affected.\n\nWhat it is: CVE-2026-67426 is a critical server-side request forgery 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-67426 exists.\n\nAffected packages and fixed versions:\n- flyto-core (PyPI): affected all versions; fixed in 2.26.7\n- flyto-core (PyPI): affected from 2.26.6; fixed in 2.26.7\n- flyto-core (PyPI): affected from 2.26.6; 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-67426/ (Markdown: https://insights.sbomify.com/CVE-2026-67426/index.md)","id":"CVE-2026-67426","markdown":"https://insights.sbomify.com/CVE-2026-67426/index.md","name":"CVE-2026-67426","record":{"aliases":["GHSA-jx74-cqjv-2c67","PYSEC-2026-3571"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Flyto2 Core","requires_auth":"none","summary":"Unauthenticated attackers can trigger SSRF and exfiltrate internal runner secrets via the verification service callback URL.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.7, the standalone flyto-verification service in src/core/verification_service.py exposes unauthenticated POST /run on 0.0.0.0:8344 and uses client-supplied callback_url for an outbound POST with X-Internal-Key: $FLYTO_RUNNER_SECRET while bypassing target_allowed, allowing unauthenticated SSRF and runner secret exfiltration. This issue is fixed in version 2.26.7.","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: Unauthenticated flyto-verification /run: callback_url SSRF and internal runner-secret exfiltration","id":"CVE-2026-67426","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Flyto2 Core: ${env.VAR} interpolation reads any env secret despite env.get being denylisted","id":"CVE-2026-67427"},"packages":[{"ecosystem":"PyPI","fixed":["2.26.7"],"introduced":["0"],"last_affected":[],"package":"flyto-core","purl":"pkg:pypi/flyto-core","source":"PYSEC-2026-3571"},{"ecosystem":"PyPI","fixed":["2.26.7"],"introduced":["2.26.6"],"last_affected":[],"package":"flyto-core","purl":null,"source":"GHSA-jx74-cqjv-2c67"},{"ecosystem":"PyPI","fixed":["2.26.7"],"introduced":["2.26.6"],"last_affected":[],"package":"flyto-core","purl":"pkg:pypi/flyto-core","source":"GHSA-jx74-cqjv-2c67"}],"prev":{"headline":"Flyto2 Core: LLM/API keys leak to an attacker-controlled base_url","id":"CVE-2026-67425"},"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":"Unauthenticated attackers can trigger SSRF and exfiltrate internal runner secrets via the verification service callback URL.","url":"https://insights.sbomify.com/CVE-2026-67426/"}