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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2026-105697)

ID	Name	Product	Family	Type	Severity
473783	SCA: security update for langflow, langflow-base, lfx (GHSA-w794-rj3p-xv45)	Tenable Cloud Security	SCA Checks	Local	critical
473783	SCA: security update for langflow, langflow-base, lfx (GHSA-w794-rj3p-xv45)	Tenable Self-Hosted Container Security	SCA Checks	Local	critical

Detections

Analytics

CVE-2026-105697

critical

Tenable Plugins

critical

critical