Description

IBM Langflow OSS 1.0.0 through 1.10.2 could allow an authenticated attacker to traverse directories on the system. An attacker could send a specially crafted URL request containing "dot dot" sequences (/../) to view arbitrary files on the system.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "6.5",
  "pubDate": "2026-09-04T17:16:51.847Z",
  "pubdate": "2026-09-04T17:16:51.847Z",
  "executiveSummary": "This vulnerability pertains to a path traversal flaw identified in IBM Langflow OSS versions 1.0.0 through 1.10.2. The security weakness allows an authenticated attacker to manipulate file path parameters by injecting directory traversal sequences, such as '../', into URL requests.\nThe primary impact of this vulnerability is the unauthorized disclosure of sensitive information, as an attacker can bypass intended access controls to retrieve arbitrary files from the underlying host filesystem. By successfully exploiting this flaw, an attacker gains read access to configuration files, system data, or sensitive application code that should otherwise remain restricted.\nThis vulnerability is categorized as an improper limitation of a pathname to a restricted directory. It requires the attacker to possess authenticated access to the application, although the specific privileges required remain consistent with standard user sessions. Successful exploitation poses a significant risk to confidentiality and system integrity, potentially facilitating further attacks through the discovery of system architecture details or credentials stored in accessible files.\nOrganizations utilizing IBM Langflow OSS within the affected version range are exposed to potential data exfiltration. Remediation requires ensuring input sanitization and enforcing strict path validation to prevent unauthorized traversal outside of designated web root directories.",
  "technicalDetails": "The vulnerability resides in the application's file handling logic, which fails to adequately sanitize user-supplied input used in file path construction. The root cause is the insufficient validation of path segments, allowing an attacker to escape the application's intended root directory context by utilizing relative path sequences, specifically the 'dot dot' (../) traversal string.\nIn IBM Langflow OSS 1.0.0 through 1.10.2, when the application processes HTTP requests involving file retrieval, the system components responsible for resource mapping fail to verify that the target file resides within an authorized directory. An authenticated attacker can craft a malicious URL containing these traversal sequences to ascend the directory tree and access sensitive files located outside the intended application directory.\nThe attack flow proceeds as follows: First, the attacker initiates an authenticated session with the target instance of IBM Langflow. Second, the attacker identifies an endpoint or a parameter that takes a filename or path as input. Third, the attacker submits a request with a manipulated path—for example, replacing a legitimate filename with a sequence such as '../../etc/passwd' or other sensitive system configuration files. Fourth, the application backend receives this input and incorrectly treats the provided string as a relative path from the current working directory. Fifth, the underlying file system API resolves the path, bypassing security boundaries, and retrieves the content of the target file.\nThis vulnerability is contingent upon the application's failure to implement robust path canonicalization or strict whitelist-based validation for file access requests. Because the system does not canonicalize the path before interaction, the traversal sequence is interpreted as a direct request for a file on the disk. The post-exploitation impact includes the potential leakage of sensitive environmental variables, configuration credentials, source code, or internal system metadata, which may allow the attacker to escalate privileges or move laterally within the environment.\nNetwork exposure is defined by the availability of the web interface to an attacker. Since authentication is a prerequisite, this flaw highlights a failure in the application's internal security controls to restrict authorized users from performing operations that exceed their intended scope of access."
}