CVE-2026-55786 (GCVE-0-2026-55786)
Vulnerability from cvelistv5 – Published: 2026-10-14 18:14 – Updated: 2026-10-14 18:14| URL | Tags |
|---|---|
| https://github.com/flytohub/flyto-core/security/a… | x_refsource_CONFIRM |
| https://github.com/flytohub/flyto-core/commit/db7… | x_refsource_MISC |
| https://github.com/flytohub/flyto-core/releases/t… | x_refsource_MISC |
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| flytohub | flyto-core |
Affected:
>= 2.26.2, < 2.26.4
|
guessed |
Previdian
Known Exploited Vulnerability - GCVE BCP-07 Compliant
Exploited: Yes
Timestamps
Scope
Evidence
Type: Public Report
Signal: Successful Exploitation
Confidence: 70%
Source: previdian
Details
| Feed | Previdian (previdian.com) |
|---|---|
| Title | Flyto2 Core - Unauthenticated OS command execution via HTTP MCP |
| Cve Id | CVE-2026-55786 |
| Vendor | Flyto2 |
| Ghsa Id | None |
| Product | flyto-core |
| Added Date | 2026-09-14T07:22:25.586Z |
| Cvss Score | 8.4 |
| Epss Score | None |
| Previous Ids | |
| Cvss Severity | HIGH |
| Virtual Patch | False |
| Cvss Estimated | False |
| Epss Percentile | None |
| Used In Malware | unknown |
| Vulnerability Id | CVE-2026-55786 |
| Ahead Of Cisa Kev | None |
| Not Yet In Cisa Kev | True |
References
{
"containers": {
"cna": {
"affected": [
{
"product": "flyto-core",
"vendor": "flytohub",
"versions": [
{
"status": "affected",
"version": "\u003e= 2.26.2, \u003c 2.26.4"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 8.4,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-78",
"description": "CWE-78: Improper Neutralization of Special Elements used in an OS Command (\u0027OS Command Injection\u0027)",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-306",
"description": "CWE-306: Missing Authentication for Critical Function",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-14T18:14:39.210Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/flytohub/flyto-core/security/advisories/GHSA-h9f9-h6gm-wc85",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/flytohub/flyto-core/security/advisories/GHSA-h9f9-h6gm-wc85"
},
{
"name": "https://github.com/flytohub/flyto-core/commit/db7f116b1d3c5dcf94aded00d14118f81f3e225e",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/flytohub/flyto-core/commit/db7f116b1d3c5dcf94aded00d14118f81f3e225e"
},
{
"name": "https://github.com/flytohub/flyto-core/releases/tag/v2.26.4",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/flytohub/flyto-core/releases/tag/v2.26.4"
}
],
"source": {
"advisory": "GHSA-h9f9-h6gm-wc85",
"discovery": "UNKNOWN"
},
"title": "Flyto2 Core: Unauthenticated Command Execution via HTTP MCP `execute_module`"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-55786",
"datePublished": "2026-10-14T18:14:39.210Z",
"dateReserved": "2026-06-17T14:40:28.380Z",
"dateUpdated": "2026-10-14T18:14:39.210Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-55786",
"date": "2026-10-21",
"epss": "0.00256",
"percentile": "0.1626"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"product": "flyto-core",
"vendor": "flytohub",
"versions": [
{
"status": "affected",
"version": "\u003e= 2.26.2, \u003c 2.26.4"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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."
}
],
"id": "CVE-2026-55786",
"lastModified": "2026-10-16T20:04:29.760",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 8.4,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.5,
"impactScore": 5.9,
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
},
"published": "2026-10-14T19:17:17.777",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/flytohub/flyto-core/commit/db7f116b1d3c5dcf94aded00d14118f81f3e225e"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/flytohub/flyto-core/releases/tag/v2.26.4"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/flytohub/flyto-core/security/advisories/GHSA-h9f9-h6gm-wc85"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-78"
},
{
"lang": "en",
"value": "CWE-306"
}
],
"source": "security-advisories@github.com",
"type": "Primary"
}
]
}
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.