Langflow Vulnerable to External Control of File Name or Path

published 2025-12-19 10 mo ago modified 2026-10-13 27 d ago also EUVD-2025-204581 , GHSA-f43r-cc68-gpx4 , PYSEC-2025-125

cvss: 7.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 5.8%; EPSS 5.8% chance of exploitation in 30 days, percentile 93%
public exploits: 0; none known

Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to version 1.7.0, if an arbitrary path is specified in the request body's `fs_path`, the server serializes the Flow object into JSON and creates/overwrites a file at that path. There is no path restriction, normalization, or allowed directory enforcement, so absolute paths (e.g., /etc/poc.txt) are interpreted as is. Version 1.7.0 fixes the issue.

Patch / fix

fixed in 3

pypi langflow 1.7.0, 1.7.1
langflow langflow 1.7.0
langflow-ai langflow 1.7.0

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: partial
Assessed: 10 mo ago (2025-12-19)

Exploit prediction

5.79% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/langflow-ai/langflow/security/advisories/GHSA-f43r-cc68-gpx4 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
GitHub	3.1	7.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
OSV	3.1	7.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

Affected packages

ecosystem	package	affected	fixed in
pypi	langflow	<1.7.1 <1.7.0	1.7.1 1.7.0

Affected products

langflow-ai langflow

Classification

Weakness

CWE-73 External Control of File Name or Path
CWE-610 Externally Controlled Reference to a Resource in Another Sphere

References

github.com /langflow-ai/langflow/security/advisories/GHSA-f43r-cc68-gpx4
exploit, web, vendor-advisory, evidence
nvd.nist.gov /vuln/detail/CVE-2025-68478
advisory
github.com /langflow-ai/langflow
package
github.com /pypa/advisory-database/tree/main/vulns/langflow/PYSEC-2025-125.yaml
web

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary