MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

Langflow discloses five CVEs against its MCP Tools component, including a critical unauthenticated code execution bug, all already fixed

IBM's CNA, which now issues security records for Langflow, published five CVE records between 2026-09-04 and 2026-09-14 against Langflow's MCP Tools component. The worst, CVE-2026-85025 (critical, 9.8), let an unauthenticated attacker execute code and tamper with chat sessions through publicly shared MCP project endpoints. Two high-severity records (8.8 each) cover separate paths to arbitrary command execution through an MCP Tools stdio subprocess configuration. All three were fixed in Langflow OSS v1.11.6, released 2026-09-01, before any of them were published. Two medium records, one narrower information-disclosure bug and one older header-spoofing bypass fixed a release earlier, round out the batch.

IBM's CNA, which now issues security records for Langflow (each description names the product "IBM Langflow OSS"), published five CVE records against Langflow's MCP Tools component between 2026-09-04 and 2026-09-14. None are cataloged here as entities.

The worst is CVE-2026-85025, critical at CVSS 3.1 9.8, reserved 2026-09-02 and published 2026-09-10. It let an unauthenticated attacker execute arbitrary code and tamper with chat sessions through publicly shared MCP project endpoints, which did not apply the same public-flow security restrictions and session isolation enforced on other anonymous execution surfaces. Two high-severity records, both 8.8, describe separate paths to command execution through the same component's stdio transport. CVE-2026-81941 let an authenticated non-admin user run arbitrary operating system commands by configuring an MCP Tools component for a local stdio subprocess, bypassing both the LANGFLOW_CUSTOM_COMPONENT_ADMIN_ONLY and LANGFLOW_BLOCK_CODE_INTERPRETER_COMPONENTS controls meant to stop exactly that. CVE-2026-78575 is a companion defect in the same configuration path: improper validation of the stdio server's command-line arguments. IBM's support page bundles all three under one bulletin and names v1.11.6 as the fix; that release published 2026-09-01, before any of the three records it closes.

CVE-2026-12763, medium at 4.2, is narrower: improper cache key isolation in the MCP Tools component let an authenticated attacker read another user's MCP server session context. It was reserved 2026-06-19 but not published until 2026-09-14, the latest date in this batch, and IBM's bulletin for it carries an initial-publication date of 2026-09-08, six days ahead of the CNA record. It is fixed in the same v1.11.6 release.

CVE-2026-9186, medium at 6.5, is the oldest and affects an earlier range, 1.0.0 through 1.11.2. A remote authenticated attacker could spoof the X-Forwarded-For: 127.0.0.1 header to bypass a localhost-only restriction on MCP configuration installation, writing to IDE config files such as ~/.cursor/mcp.json. It was published 2026-09-04 and fixed one release earlier than the rest, in v1.11.3 on 2026-08-11.

How was this verified, and what are the sources?

Published · last verified · confidence 1.00.

  1. CVE-2026-85025 CNA record (ibm) - "IBM Langflow OSS 1.0.0 through 1.11.5 Langflow could allow an unauthenticated attacker to execute arbitrary code and access or modify chat sessions through publicly shared MCP project endpoints due to improper enforcement of public-flow security restrictions and session isolation controls"; CVSS 3.1 9.8 critical; datePublished 2026-09-10, dateReserved 2026-09-02 - accessed
  2. IBM Security Bulletin (node/7286666) - covers CVE-2026-85025, CVE-2026-81941, and CVE-2026-78575 together; remediation "upgrading Langflow OSS to version 1.11.6"; mechanism text describes the MCP stdio validator, the code security scanner, and the public-flow execution guard as the incomplete controls involved - accessed
  3. CVE-2026-81941 CNA record (ibm) - "an authenticated non-administrative user could execute arbitrary operating system commands ... by constructing a flow with an MCP Tools component configured to use a local stdio subprocess transport. This bypasses both the LANGFLOW_CUSTOM_COMPONENT_ADMIN_ONLY and LANGFLOW_BLOCK_CODE_INTERPRETER_COMPONENTS server-side controls"; CVSS 3.1 8.8 high; datePublished 2026-09-10, dateReserved 2026-08-27 - accessed
  4. CVE-2026-78575 CNA record (ibm) - "could allow a remote authenticated attacker to execute arbitrary commands due to improper validation of command-line arguments in the MCP stdio server configuration"; CVSS 3.1 8.8 high; datePublished 2026-09-10, dateReserved 2026-08-24 - accessed
  5. CVE-2026-12763 CNA record (ibm) - "could allow an authenticated attacker to access another user's MCP server context due to improper cache key isolation in the MCP Tools component"; CVSS 3.1 4.2 medium; datePublished 2026-09-14, dateReserved 2026-06-19, the latest date in this batch - accessed
  6. IBM Security Bulletin (node/7286662) - covers CVE-2026-12763; remediation "upgrading Langflow OSS to version 1.11.6"; initial publication dated 08 Sep 2026, six days before the CNA record published - accessed
  7. CVE-2026-9186 CNA record (ibm) - "allows remote authenticated attackers to bypass localhost-only MCP configuration installation by spoofing X-Forwarded-For: 127.0.0.1 header, enabling arbitrary writes to IDE config files (~/.cursor/mcp.json, etc.)"; CVSS 3.1 6.5 medium; affected 1.0.0 through 1.11.2; datePublished 2026-09-04, dateReserved 2026-05-21; IBM's companion bulletin (node/7285646) names the fix as v1.11.3 - accessed
  8. langflow-ai/langflow releases - v1.11.6 published 2026-09-01T02:21:38Z, the fix for the three MCP Tools code-execution records; v1.11.3 published 2026-08-11T23:14:46Z, the fix for CVE-2026-9186 - accessed

← All news