flyto-core Exposed Commands
flyto-core protected its REST execution route but left HTTP POST /mcp unauthenticated. The repository advisory, published 30 May 2026, identifies versions 2.26.2 to before 2.26.4 as affected and 2.26.4 as fixed. Calls could reach a shell module and run commands with the server process’s privileges.
For CVE-2026-55786, default loopback binding limits reach; a non-loopback listener can expose the flaw to the network. The root-in-container demonstration proves neither host-root access nor malicious exploitation.
Check the deployment, not the label
Upgrade to 2.26.4 or later, then safely verify rejection of unauthenticated execution. Check listener exposure and process privileges, including on developer workstations.
For an incident handover, distinguish three entries: what was observed, what was tested and what remains unknown. A test result belongs with its date and deployment identity. That makes a later reviewer less likely to mistake a clean replacement environment for evidence about an earlier one. Missing alerts alone cannot settle that earlier environment’s history.
BlackTree’s Chainlit MCP report covers a different product. Its fix does not resolve this vulnerability.
