{"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-55787 exists.","fix":"Upgrade flyto-core to 2.26.3 or later.","what":"CVE-2026-55787 is a high-severity server-side request forgery vulnerability in flytohub flyto-core, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-55787 and fix it if it is affected.\n\nWhat it is: CVE-2026-55787 is a high-severity server-side request forgery vulnerability in flytohub flyto-core, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55787 exists.\n\nAffected packages and fixed versions:\n- flyto-core (PyPI): affected all versions; fixed in 2.26.3\n- flyto-core (PyPI): affected all versions; fixed in 2.26.3\n- flyto-core (PyPI): affected all versions; fixed in 2.26.3\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-55787/ (Markdown: https://insights.sbomify.com/CVE-2026-55787/index.md)","id":"CVE-2026-55787","markdown":"https://insights.sbomify.com/CVE-2026-55787/index.md","name":"CVE-2026-55787","record":{"aliases":["GHSA-794r-5rp2-fpg8","PYSEC-2026-2481"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Flyto2 Core","requires_auth":"low_privilege","summary":"Authenticated users can bypass SSRF protections using IPv6 transition addresses to access internal services and cloud metadata.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.3, validate_url_ssrf and is_private_ip in src/core/utils.py compare resolved addresses only against native private IPv4 and IPv6 ranges and do not unwrap IPv4-mapped, IPv4-compatible, 6to4, or NAT64 transition addresses. An authenticated workflow author can provide a transition-form literal URL through the Execution API POST /v1/execute route, http.get, or sibling guarded outbound-request modules, causing the guard to accept an address whose embedded IPv4 points to loopback, RFC 1918, or cloud metadata services. On a host that routes the selected transition form, the outbound request reaches the internal destination and returns the response body to the workflow caller, enabling read SSRF and disclosure of internal-service data or cloud credentials. This issue is fixed in version 2.26.3.","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: SSRF guard bypass via IPv6 transition addresses (IPv4-mapped / 6to4 / NAT64) in validate_url_ssrf","id":"CVE-2026-55787","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Code injection in logto","id":"CVE-2026-55789"},"packages":[{"ecosystem":"PyPI","fixed":["2.26.3"],"introduced":["0"],"last_affected":[],"package":"flyto-core","purl":null,"source":"GHSA-794r-5rp2-fpg8"},{"ecosystem":"PyPI","fixed":["2.26.3"],"introduced":["0"],"last_affected":[],"package":"flyto-core","purl":"pkg:pypi/flyto-core","source":"GHSA-794r-5rp2-fpg8"},{"ecosystem":"PyPI","fixed":["2.26.3"],"introduced":["0"],"last_affected":[],"package":"flyto-core","purl":"pkg:pypi/flyto-core","source":"PYSEC-2026-2481"}],"prev":{"headline":"Flyto2 Core: Unauthenticated Command Execution via HTTP MCP `execute_module`","id":"CVE-2026-55786"},"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":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["flytohub"]},"summary":"Authenticated users can bypass SSRF protections using IPv6 transition addresses to access internal services and cloud metadata.","url":"https://insights.sbomify.com/CVE-2026-55787/"}