IBM Langflow OSS Vulnerability Allows Arbitrary File Writes

IBM Langflow OSS versions 1.0.0 through 1.10.0 contain a critical path traversal vulnerability, tracked as CVE-2026-8859, which carries a CVSS score of 9.9. The flaw resides in the APIRequest component and allows an attacker to write arbitrary files to unintended locations on the host server by exploiting improper input validation within the 'Save to File' feature.

What's at Risk

This vulnerability affects all deployments of IBM Langflow OSS within the 1.0.0 to 1.10.0 version range. Organizations utilizing these versions, particularly those with internet-facing deployments or those that process data from external, untrusted HTTP servers, are at significant risk of system compromise.

Because the vulnerability allows for arbitrary file writes, an attacker could potentially overwrite critical system configuration files, inject malicious scripts, or place executable payloads in startup directories to achieve remote code execution. Systems exposed to the public internet are at the highest level of risk, as they provide an accessible vector for attackers to trigger the malicious APIRequest sequence.

How the Flaw Works

Path traversal vulnerabilities, also known as directory traversal, occur when an application fails to properly sanitize user-supplied input before using it to construct a file path. In general, this class of weakness allows an attacker to escape the intended directory structure by including sequences such as '../' in their input, which forces the operating system to navigate to unauthorized areas of the file system.

When an application blindly trusts file names provided by external sources—such as those found in HTTP headers like Content-Disposition—it creates a bridge between the application's temporary storage and the host's sensitive directories. By manipulating these headers, an attacker can trick the application into writing files into locations they should not have access to, effectively bypassing standard security boundaries designed to protect the integrity of the host environment.

How to Protect Your Systems

• Upgrade IBM Langflow OSS to a version beyond 1.10.0 immediately to remediate the vulnerability.
• Restrict network access to the Langflow instance, ensuring it is not directly exposed to the public internet.
• Implement strict input validation and sanitization policies for all external data sources handled by the application.
• Monitor server logs for suspicious Content-Disposition header activity or unexpected file creation events in sensitive directories.
• Follow standard vendor hardening guides to ensure the application runs with the least privilege necessary, minimizing the impact if a compromise occurs.

Given the critical severity of this flaw and the potential for full system compromise, organizations should prioritize patching as an immediate requirement. Failure to address this vulnerability leaves the underlying infrastructure exposed to attackers capable of leveraging path traversal to gain persistent, unauthorized access to the server environment.