CVE-2026-105697
CRITICALDescription
Langflow is a tool for building and deploying AI-powered agents and workflows. Before Langflow 1.10.3, the MCP stdio transport launched whatever command / args a user put in an MCP server configuration, with no allowlist and (before 1.10.3) wrapped in bash -c "exec {command} ...". Any user able to reach the MCP server settings ("Settings → MCP Servers → Add MCP Server", POST/PATCH /api/v2/mcp/servers/{server_name}) or to build a flow with the MCP Tools component could add a "server" whose command is an arbitrary OS command (touch, rm -rf, a reverse shell, ...). The command runs on the Langflow host as the Langflow process user as soon as Langflow tries to connect to the server (listing servers, loading tools, running the flow) — even when the UI then reports that the stdio server failed to start. With the default LANGFLOW_AUTO_LOGIN=true, GET /api/v1/auto_login hands out a token without credentials, so on an exposed instance running the default configuration this is reachable without an account. AUTO_LOGIN is documented as a development-only setting; with it disabled, any authenticated (non-admin) user can exploit it. This issue is fixed in Langflow 1.10.3, langflow-base 0.10.3, and lfx 1.10.3.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 32% of all known CVEs.
References
Related Vulnerabilities
Other CWE-78 (OS Command Injection) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2021-1498 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2014-6271 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2019-16920 | Critical | 9.8 | 100% | KEV | - |
| CVE-2022-44877 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2020-8515 | Critical | 9.8 | 100% | KEV | - |
| CVE-2020-9054 | Critical | 9.8 | 100% | KEV | Fix |
Common questions
How do I fix CVE-2026-105697?
No published fix for CVE-2026-105697 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-105697 being actively exploited?
Not that we know of. CVE-2026-105697 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.40% is the estimated probability that it will be exploited in the next 30 days. That is higher than 32% of all scored CVEs.
How severe is CVE-2026-105697?
CVE-2026-105697 has a CVSS v3 base score of 9.9, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-105697
Markdown
[](https://tridentstack.com/cve/CVE-2026-105697)HTML
<a href="https://tridentstack.com/cve/CVE-2026-105697"><img src="https://tridentstack.com/cve/badge/CVE-2026-105697.svg" alt="CVE-2026-105697"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-09.