Secure Autonomous
FeedbackGet alertsCheck a deployment
Signals › SIG-2026-10-15-002

CVE-2026-55786: Flyto2 Core

The National Vulnerability Database (NVD) records that from 2.26.2 until 2.26.4 Flyto2 Core's HTTP Model Context Protocol (MCP) route accepted unauthenticated tools/call requests that could reach its shell-execution module and run operating-system commands; fixed in 2.26.4.

VulnerabilitySoftware agents · Enterprise work agentsRecord published 2026-10-14Posted 2026-10-15
SIG-2026-10-15-002National Vulnerability Database record ↗

The record

Kind
Vulnerability
Source record
CVE-2026-55786: Flyto2 Core is an execution kernel for automation and AI-agent workflows. From 2.26.2 until 2.26.4, the HTTP M (National Vulnerability Database record)
Record published
2026-10-14
Posted here
2026-10-15
World
Software agents · Enterprise work agents
Controls concerned
Authority binding C-A2; Containment and isolation C-E5
Checked
Checked against its record on 2026-10-22 by a reader who did not draft it; report verification/reports/SIG-2026-10-15-002-2026-10-22.md.

A signal's controls are the ones its record points at, the exposure; a case's controls are the ones its records show were absent or failed, so the two can differ.

Corrections

Changes to what this signal says, with the reason. Every earlier version is kept.

What a signal is. A signal records what a primary record says; it assigns no fault. It is lighter than a case: one dated item from one record, tagged with the world, sector and controls it touches. It becomes a case when it meets the bar for one.

New signals like this, once a week. A short email when a case, signal or rule touches software agents. Free; unsubscribe in one click.

Get the weekly email

Newer: CVE-2026-76066: IntentKit
Older: CVE-2026-110616: NullHub

Is this wrong? Dispute it with the record that shows otherwise. All signals · RSS feed.

Help shape the Register

A person reads every answer; changes it leads to are logged in the methodology. To dispute a claim or reply for a named company, use Respond, dispute, or submit.

Did this page help with what you came to do?