IBM Langflow OSS vulnerabilities

IBM Langflow OSS versions 1.0.0 through 1.10.3 (repeated) could allow a remote authenticated attacker to execute arbitrary commands due to improper neutralization of special elements used in an OS command.

IBM Langflow OSS 1.0.0 through 1.10.3 allows remote authenticated attackers to bypass localhost-only restrictions and write arbitrary MCP server configurations to IDE configuration files on the host system.

IBM Langflow OSS 1.0.0 through 1.10.3 contain an authentication bypass vulnerability in the Model Context Protocol (MCP) composer endpoint when mcp_composer_enabled=true (default) and projects are configured with auth_type=oauth.

IBM Langflow OSS versions 1.0.0 through 1.10.1 allow an attacker to access another user's private vector documents by creating their own flow with matching Chroma persist_directory and collection_name values. The attacker receives exact victim content in their workflow output despite having no authorization to read the victim's flow. Additionally, the attacker can pollute the victim's collection by inserting their own documents into the shared namespace.

IBM Langflow OSS versions 1.0.0 through 1.10.1 allow a remote attacker to traverse directories on the system. An attacker can send a specially crafted URL request containing "dot dot" sequences ( /../ ) to view arbitrary files.

IBM Langflow OSS 1.0.0 through 1.10.1 allows authenticated users to access and manipulate other users' build jobs through improper access control on log retrieval and unauthenticated build endpoints.

IBM Langflow OSS versions 1.0.0 through 1.10.1 allow an attacker to reuse another user's FAISS namespace to access owner-only vector content and influence later query results. This causes cross-user information disclosure and limited integrity impact through persistent poisoning of returned results.

IBM Langflow OSS versions 1.0.0 through 1.10.1 allow an authenticated attacker to exploit the SaveToFile component to read and modify another user's uploaded files by specifying absolute paths to victim storage locations. In append mode, the attacker reads victim file contents, appends own data, and uploads a copy to their namespace. In overwrite mode, they can replace victim file contents with arbitrary data.

IBM Langflow OSS versions 1.0.0 through 1.10.0 allow authenticated users to override component parameters at runtime via the API. A critical security flaw exists in the parameter filtering mechanism within the `apply_tweaks()` function.

IBM Langflow OSS versions 1.0.0 through 1.10.0 contain a vulnerability that allows an authenticated attacker to read arbitrary files, including the JWT signing key, and then forge authentication tokens for any user.

Vulnerability in IBM Langflow OSS (versions 1.0.0-1.10.0) allows an authenticated attacker to create a malicious flow that writes arbitrary files to the system via a crafted Content-Disposition header.

IBM Langflow OSS versions 1.0.0 through 1.10.1 contain a vulnerability in the Python Interpreter component. An authenticated user can exploit improper input validation to execute arbitrary commands with elevated privileges.

IBM Langflow OSS versions 1.0.0 through 1.10.1 contain an unauthenticated remote code execution vulnerability in the public flow build endpoint (/api/v1/build_public_tmp/{flow_id}/flow). The vulnerability stems from an incomplete denylist in the validate_public_flow_no_code_execution() function that fails to block several code-execution agent components including OpenDsStarAgent, CodeActAgentSmolagents, and CSVAgent.

IBM Langflow OSS versions 1.0.0 through 1.9.6 contain a Server-Side Request Forgery (SSRF) vulnerability. The RSSReaderComponent and SearXNG components make unvalidated HTTP requests to user-controlled URLs, bypassing SSRF protections introduced in version 1.9.3.

IBM Langflow OSS versions 1.0.0 through 1.9.6 contain a missing authentication vulnerability in /api/v1/build_public_tmp/ endpoints, allowing an unauthenticated attacker to read build event data or cancel jobs using a valid job identifier, resulting in information disclosure and denial of service.

IBM Langflow OSS versions 1.0.0 through 1.9.3 contain a Server-Side Request Forgery (SSRF) vulnerability in the URL component due to a TOCTOU race condition exploitable via DNS rebinding.

IBM Langflow OSS versions 1.0.0 through 1.9.3 contain a Server-Side Request Forgery (SSRF) protection bypass vulnerability in the API Request component. An authenticated attacker with low-level privileges (flow author role) can bypass SSRF protections by enabling the follow_redirects parameter and supplying a public URL that redirects to internal/localhost addresses. The vulnerability exists because the application validates only the initial URL but does not re-validate redirect destinations.

IBM Langflow OSS versions 1.0.0 through 1.9.1 could allow an authenticated user to read or modify sensitive information by bypassing authentication using insecure direct object references.