CVE-2026-18894

Langflow OSS is affected by multiple vulnerabilities

Published Oct 29, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
IBM Langflow OSS 1.0.0 through 1.12.4 could allow a remote attacker to trigger pre-existing stored Python component code in a public workflow, executing it under the flow owner's runtime context within the server process. This bypasses the intended trust boundary where public execution paths are restricted to server-trusted component code.

Analysis

AI-generated

Technical impact

The vulnerability allows a remote attacker to trigger the execution of pre‑existing stored Python component code within a public workflow on IBM Langflow OSS. This code runs under the flow owner’s runtime context inside the server process, bypassing the intended trust boundary that should confine execution to server‑trusted components. The result is the attacker can execute arbitrary code on the server with the privileges of the flow owner, potentially leading to full system compromise.

Affected Systems

IBM Langflow OSS versions 1.0.0 through 1.12.4 are affected. The fix is provided in version 1.12.5 and earlier successful releases 1.11.2, 1.11.5 for related issues. Apply the upgrade to remove this vulnerability.

Risk and Exploitability

The CVSS score of 6.5 indicates moderate risk, and the EPSS score is currently unavailable. The vulnerability is not listed in the CISA KEV catalog. Attackers would need to publish a malicious public workflow containing a component that contains the malicious code. Once accessed, the code executes in the server context with flow owner privileges, providing a direct remote code execution vector.

Remediation

Vendor Solution

IBM strongly recommends addressing the vulnerability now by upgrading Langflow OSS to version 1.12.5. https://pypi.org/project/langflow/1.12.5/ For Langflow OSS versions 1.0.0 - 1.12.4, follow the Prepare to upgrade instructions and release-specific configuration changes https://docs.langflow.org/release-notes , including backing up your existing installation, then follow the Langflow OSS installation instructions https://docs.langflow.org/get-started-installation to install version 1.12.5 and test your flows. For deployments using MCP stdio, also apply the configuration controls in Workarounds and Mitigations. This bulletin also discloses fixes delivered in prior releases: CVE-2026-107366 was fixed in version 1.9.0; CVE-2026-18894 was fixed in version 1.11.2; and CVE-2026-77817 was fixed in version 1.11.5. Version 1.12.5 includes these fixes.


Vendor Workaround

IBM strongly recommends applying the following configuration controls to deployments using MCP stdio in addition to upgrading Langflow OSS to version 1.12.5. These controls do not replace the upgrade. Set LANGFLOW_MCP_SERVER_INTERPRETER_HARDENING=true to reject direct shell-script execution, and set LANGFLOW_CUSTOM_COMPONENT_ADMIN_ONLY=true to block non-admin MCP stdio access. Restart the Langflow service after updating its environment configuration. These restrictions can require changes to existing MCP server launch configurations and limit which users can use MCP stdio. For public workflows, retain the default restriction on custom components. Explicitly enabling LANGFLOW_ALLOW_PUBLIC_CUSTOM_COMPONENTS permits custom component execution and changes the default protection described for CVE-2026-18894. For CVE-2026-77817, upgrading prevents the identified secret disclosure in new flow and project exports. Revoke or rotate any credentials exposed in previously exported files; upgrading does not remove secrets from copies already exported.


OpenCVE Recommended Actions

  • Upgrade IBM Langflow OSS to version 1.12.5 or later.
  • For deployments using MCP stdio, set LANGFLOW_MCP_SERVER_INTERPRETER_HARDENING=true and LANGFLOW_CUSTOM_COMPONENT_ADMIN_ONLY=true in the environment variables, then restart the Langflow service. Fine‑tune any MCP server launch configurations to accommodate these settings.
  • Maintain the default restriction for public workflows; do not enable LANGFLOW_ALLOW_PUBLIC_CUSTOM_COMPONENTS unless absolutely required.
  • Revoke or rotate credentials that may have been exposed in previously exported flow or project files, noting that the upgrade does not erase secrets already present in older exports.

Generated by OpenCVE AI on October 29, 2026 at 17:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Langflow
Langflow langflow
CPEs cpe:2.3:a:langflow:langflow:*:*:*:*:*:*:*:*
Vendors & Products Langflow
Langflow langflow
Type Values Removed Values Added
Description IBM Langflow OSS 1.0.0 through 1.12.4 could allow a remote attacker to trigger pre-existing stored Python component code in a public workflow, executing it under the flow owner's runtime context within the server process. This bypasses the intended trust boundary where public execution paths are restricted to server-trusted component code.
Title Langflow OSS is affected by multiple vulnerabilities
First Time appeared Ibm
Ibm langflow Oss
Weaknesses CWE-94
CPEs cpe:2.3:a:ibm:langflow_oss:1.0.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:langflow_oss:1.12.4:*:*:*:*:*:*:*
Vendors & Products Ibm
Ibm langflow Oss
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'}

Weaknesses
  • CWE-94

    Improper Control of Generation of Code ('Code Injection')

Sources

Status
PUBLISHED
Assigner
ibm
Published
Updated
Oct 29, 2026, 7:38 PM
Reserved
Aug 4, 2026, 7:51 PM
Status
Analyzed
Published
Oct 29, 2026, 4:18 PM
Modified
Oct 30, 2026, 1:23 PM