{"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-55786 exists.","fix":"Upgrade flyto-core to 2.26.4 or later.","what":"CVE-2026-55786 is a high-severity command injection vulnerability in flytohub flyto-core, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-55786 and fix it if it is affected.\n\nWhat it is: CVE-2026-55786 is a high-severity command injection vulnerability in flytohub flyto-core, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55786 exists.\n\nAffected packages and fixed versions:\n- flyto-core (PyPI): affected from 2.26.2; fixed in 2.26.4\n- flyto-core (PyPI): affected from 2.26.2; fixed in 2.26.4\n- flyto-core (PyPI): affected from 2.26.2; fixed in 2.26.4\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-55786/ (Markdown: https://insights.sbomify.com/CVE-2026-55786/index.md)","id":"CVE-2026-55786","markdown":"https://insights.sbomify.com/CVE-2026-55786/index.md","name":"CVE-2026-55786","record":{"aliases":["GHSA-h9f9-h6gm-wc85","PYSEC-2026-2482"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python automation kernel","requires_auth":"none","summary":"Unauthenticated attackers can execute arbitrary OS commands via the HTTP MCP endpoint in Flyto2 Core, leading to potential host compromise.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Flyto2 Core is an execution kernel for automation and AI-agent workflows. From 2.26.2 until 2.26.4, the HTTP MCP POST /mcp route accepts unauthenticated JSON-RPC tools/call requests and forwards execute_module arguments to the module registry without the require_auth dependency used by the REST execution routes. An unauthenticated caller can select sandbox.execute_shell and supply its command parameter, which reaches asyncio.create_subprocess_shell with the privileges of the flyto-core server process. The endpoint is reachable locally under the default loopback binding and becomes network reachable when an operator binds the server to a non-loopback interface, allowing arbitrary OS command execution and potential full host compromise. This issue is fixed in version 2.26.4.","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 Command Execution via HTTP MCP `execute_module`","id":"CVE-2026-55786","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Flyto2 Core: SSRF guard bypass via IPv6 transition addresses (IPv4-mapped / 6to4 / NAT64) in validate_url_ssrf","id":"CVE-2026-55787"},"packages":[{"ecosystem":"PyPI","fixed":["2.26.4"],"introduced":["2.26.2"],"last_affected":[],"package":"flyto-core","purl":null,"source":"GHSA-h9f9-h6gm-wc85"},{"ecosystem":"PyPI","fixed":["2.26.4"],"introduced":["2.26.2"],"last_affected":[],"package":"flyto-core","purl":"pkg:pypi/flyto-core","source":"GHSA-h9f9-h6gm-wc85"},{"ecosystem":"PyPI","fixed":["2.26.4"],"introduced":["2.26.2"],"last_affected":[],"package":"flyto-core","purl":"pkg:pypi/flyto-core","source":"PYSEC-2026-2482"}],"prev":{"headline":"free5GC AUSF uses non-constant-time authentication comparisons and logs XRES* in 5G-AKA","id":"CVE-2026-55785"},"products":["flyto-core"],"published":"2026-10-14","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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["flytohub"]},"summary":"Unauthenticated attackers can execute arbitrary OS commands via the HTTP MCP endpoint in Flyto2 Core, leading to potential host compromise.","url":"https://insights.sbomify.com/CVE-2026-55786/"}