{"cvss":8.4,"datePublished":"2026-09-14T00:00:00Z","dateUpdated":"2026-09-14T00:00:00Z","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.","dueDate":"","id":"CVE-2026-55786","kev_catalogs":["vulncheck"],"knownRansomwareCampaignUse":"Unknown","product":"Flyto2 Core","requiredAction":"Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.","severity":"HIGH","source":"vulncheck_kev","title":"  Improper Neutralization of Special Elements used in an OS Command","vendor":"FlytoHub"}