langflow-ai · Langflow · published 2026-10-05

CVE-2026-105697Langflow: OS command injection (RCE) via arbitrary command in MCP stdio server configuration

This month EPSS 1.5% with high severity (CVSS 9.9).

CVE-2026-105697 is not known to be exploited in the wild. EPSS estimates a 1.5% chance of exploitation in the next 30 days, higher than 74% of all CVEs. This Langflow vulnerability: CVSS 9.9 (v3.1), a successful attack gives total control of the component. Fixed upstream in Langflow 1.12.0, 1.10.3, 1.10.1, 0.10.3 (+2 more). Patch in your normal monthly cycle.

Share this

Remediation#

Fixed upstream in Langflow 1.12.0, 1.10.3, 1.10.1, 0.10.3, 0.10.1, 0.1.2.

Patch events

  1. This monthSecurity release

    AI toolingLangflow

    Langflow security fixes: 2 CVEs

    Upgrade to 1.12.01.10.31.10.10.10.30.10.10.1.2

    Why: CVE-2026-105697: EPSS 1.5% with high severity (CVSS 9.9).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)1.5% (75th pct)FIRST EPSS v2026.06.15
CVSS base score9.9 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →