IBM Langflow OSS EUVD-2026-71270

Exploitation requires a valid authenticated session on IBM Langflow OSS with at least low-privilege access (confirmed by PR:L in the CVSS vector). The Langflow service must be reachable over the network (AV:N). No user interaction beyond the attacker's own requests is required (UI:N). Unauthenticated attackers cannot exploit this directly. The specific endpoint or feature handling the vulnerable file-path parameter is not identified in available data; the scope of readable files is bounded by the OS-level permissions of the Langflow process user. Versions outside the range 1.0.0-1.11.2 are not confirmed affected.

The CVSS 6.5 score correctly reflects a confidentiality-only impact (C:H/I:N/A:N) gated behind authenticated access (PR:L). The PR:L requirement is the primary risk-moderating factor: an attacker must first obtain valid Langflow credentials before path traversal can be attempted. The low attack complexity (AC:L) and network attack vector (AV:N) mean that once credentials are in hand, exploitation is mechanically straightforward with no special conditions. No EPSS score was supplied, and this CVE does not appear in CISA KEV, suggesting no confirmed widespread exploitation. SSVC signals: exploitation status is none known, automatable only after credential compromise, technical impact partial (C:H only). Overall this is a genuine medium-severity issue warranting patch priority in multi-tenant or externally-exposed Langflow deployments, but not an emergency for internally-hosted instances with strong access control.

An attacker with a valid low-privilege account on an exposed IBM Langflow OSS instance crafts an API request embedding directory traversal sequences (e.g., '../../../../etc/passwd' or paths targeting application config files containing secrets) in a file-path parameter. The server fails to canonicalize the path before resolving it, returning the content of the targeted file. No public exploit or proof-of-concept has been identified at time of analysis.