IBM Langflow Desktop CVE-2026-3345

Authentication is required - the attacker must possess valid credentials or an authenticated session to Langflow Desktop (PR:L in CVSS vector). The vulnerability does not require special application configuration or feature enablement; it is inherent to how the file handling mechanism processes URL paths. The exploitation is further limited by what files are readable by the Langflow process user account - files outside that permission scope remain inaccessible. Network access to the Langflow Desktop service is required; the service must be exposed either directly over the network or accessible via proxy/forwarding.

CVSS 6.5 with AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N indicates network-accessible path traversal requiring low-privilege authentication. The HIGH confidentiality impact reflects unrestricted file read access, but no integrity or availability impact. EPSS score data is not provided, limiting quantitative exploitation probability assessment. CISA KEV status and POC availability are not indicated in the provided intelligence. The authentication requirement (PR:L) is a meaningful constraint - the attacker must have valid credentials or authenticated access to Langflow Desktop, reducing the immediate threat surface compared to unauthenticated path traversal. However, in environments where Langflow Desktop is accessible to many internal users or where default credentials are in use, this becomes a significant lateral movement or privilege escalation vector. The AC:L (low complexity) indicates a straightforward exploitation technique requiring no special conditions beyond crafting a simple URL. Risk priority depends on: (1) whether Langflow Desktop is network-exposed or internal-only, (2) how strictly authentication/access controls are enforced, and (3) what sensitive files are readable by the Langflow process user account.

A developer with valid credentials to IBM Langflow Desktop on an internal server could craft a URL such as 'http://langflow-host:port/api/files?path=../../../../../../etc/passwd' to read system configuration files. Alternatively, an attacker who obtains valid credentials through phishing or credential compromise could exploit this remotely to exfiltrate configuration files, API keys, or source code stored in the Langflow working directory or parent directories.