Is CVE-2026-55786 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-55786 being exploited in the wild.

How severe is CVE-2026-55786?

High severity, with a CVSS score of 8.4, published 14 October 2026.

Which products and versions are affected?

flyto-core (PyPI) >= 2.26.2, < 2.26.4, ECOSYSTEM:introduced=2.26.2,fixed=2.26.4.

Is there a fix for CVE-2026-55786?

Yes. flyto-core (PyPI): upgrade to 2.26.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-55786 attacked?

It is attacked over the network or with local access, in a software library.

Am I affected by CVE-2026-55786?

Check whether you run flyto-core (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55786: flytohub flyto-core unauthenticated command execution in HTTP MCP

Q: Is there a fix for CVE-2026-55786?

Yes. flyto-core (PyPI): upgrade to 2.26.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-55786 attacked?

It is attacked over the network or with local access, in a software library.

Q: Am I affected by CVE-2026-55786?

Check whether you run flyto-core (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55786 · Severity: high · CVSS 8.4 · Published 2026-10-14

flyto-core, a library used for building AI-driven applications, contains a security flaw in its communication interface. An attacker can send specially crafted messages to the server to execute arbitrary commands on the underlying operating system without needing a password. This could lead to a complete takeover of the server, allowing unauthorized access to sensitive data or the ability to disrupt operations.

Technologies: flyto-core (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-55786 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55786 being exploited in the wild.
How severe is CVE-2026-55786?: High severity, with a CVSS score of 8.4, published 14 October 2026.
Which products and versions are affected?: flyto-core (PyPI) >= 2.26.2, < 2.26.4, ECOSYSTEM:introduced=2.26.2,fixed=2.26.4.
Is there a fix for CVE-2026-55786?: Yes. flyto-core (PyPI): upgrade to 2.26.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55786 attacked?: It is attacked over the network or with local access, in a software library.
Am I affected by CVE-2026-55786?: Check whether you run flyto-core (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

flyto-core (PyPI): upgrade to 2.26.4 or later
```
pip install "flyto-core>=2.26.4"
```

Technical details

The HTTP Model Context Protocol (MCP) endpoint (`POST /mcp`) in flyto-core fails to implement authentication checks, unlike other REST routes. The endpoint accepts JSON-RPC `tools/call` requests and dispatches them to registered modules. Specifically, the `execute_module` tool can be used to invoke the `sandbox.execute_shell` module, which passes unsanitized attacker input directly to `asyncio.create_subprocess_shell`. While the server binds to the loopback interface by default (local attack vector), it is remotely exploitable if configured to listen on all interfaces. The vulnerability allows full system compromise with the privileges of the server process (e.g., root). A fix is available in version 2.26.4.

Affected products

flytohub flyto-core >= 2.26.2, < 2.26.4

Identifiers

CVE-2026-55786
GHSA-h9f9-h6gm-wc85
PYSEC-2026-2482

Timeline

2026-05-30: disclosed
2026-07-06: advisory: GHSA-h9f9-h6gm-wc85 published
2026-07-06: patched: Version 2.26.4 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.