Skip to main content

Langflow EUVDEUVD-2026-38511

| CVE-2026-55450 CRITICAL
Information Exposure (CWE-200)
2026-06-17 https://github.com/langflow-ai/langflow GHSA-x223-p2gf-v735
9.3
CVSS 3.1 · Vendor: https://github.com/langflow-ai/langflow
Share

Severity by source

Vendor (https://github.com/langflow-ai/langflow) PRIMARY
9.3 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:H
vuln.today AI
9.3 CRITICAL

Remote, unauthenticated, no interaction (AV:N/AC:L/PR:N/UI:N); disk-exhaustion DoS gives A:H and affects the host beyond the app (S:C); path leak is C:L; no integrity impact (I:N).

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (https://github.com/langflow-ai/langflow).

CVSS VectorVendor: https://github.com/langflow-ai/langflow

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
High

Lifecycle Timeline

3
Source Code Evidence Fetched
Jun 18, 2026 - 01:38 vuln.today
Analysis Generated
Jun 18, 2026 - 01:38 vuln.today
CVE Published
Jun 17, 2026 - 18:43 github-advisory
CRITICAL 9.3

DescriptionCVE.org

Summary

Unauthenticated users can upload any amount of data to the server without any limitations. No need for any prior knowledge, only network access to Langflow.

This can lead to space exhaustion on the server.

In adition, in the response, the absolute path of the uploaded file is reported to the attacker, which is an information leak that can assist in chaining other primitives.

Tested on commit 2d67402b1dbaefcbce85a244d4a6cd5e4bda1cfe

Details

Code is in langflow/api/v1/endpoints.py:

python
@router.post(
    "/upload/{flow_id}",
    status_code=HTTPStatus.CREATED,
    deprecated=True,
)
async def create_upload_file(
    file: UploadFile,
    flow_id: UUID,
) -> UploadFileResponse:
...

As can be seen above, there is no authentication. There is not validation over flow_id as well, unlike other endpoints:

        flow_id_str = str(flow_id)
        file_path = await asyncio.to_thread(save_uploaded_file, file, folder_name=flow_id_str)

Function save_uploaded_file saves the file to local file-system. Suggested fix:

  1. Add authentication to route.
  2. Only return relative path or filename.

PoC

PoC:

bash
curl 'http://localhost:7860/api/v1/upload/<any_uuid>' -F "file=@<any_file>"

Example:

bash
# curl 'http://localhost:7860/api/v1/upload/11111111-1111-1111-1111-111111111111' -F "file=@/tmp/dummy.txt"
{"flowId":"11111111-1111-1111-1111-111111111111","file_path":"/Users/ori/Library/Caches/langflow/11111111-1111-1111-1111-111111111111/9d63c3b5b7623d1fa3dc7fd1547313b9546c6d0fbbb6773a420613b7a17995c8.txt"}

Impact

  1. Space exhaustion on server that can lead to Denial-of-Service.
  2. Information leak - leakage of absolute path of langflow's cache directory in server.

Patches

Fixed in 1.9.1 via PR #12831. The deprecated POST /api/v1/upload/{flow_id} endpoint now uses the get_flow dependency, requiring an authenticated user and flow ownership (returns 404 for missing or cross-user flows), and enforces the max_file_size_upload limit (HTTP 413) - closing the unauthenticated upload and disk-exhaustion vectors. Upgrade to 1.9.1 or later.

Note: the response still returns the file's absolute path (file_path); after this fix it is only disclosed to the authenticated owner of the flow.

Ori Lahav Security Researcher @ Rubrik Inc.

AnalysisAI

Unauthenticated file upload in Langflow before 1.9.1 lets any network-reachable attacker POST arbitrary files to the deprecated /api/v1/upload/{flow_id} endpoint with no credentials, no flow_id validation, and no size limit, enabling disk exhaustion (denial of service) and leaking the server's absolute cache path in the JSON response. Publicly available proof-of-concept exists (a single curl command), SSVC rates it automatable with partial technical impact, but there is no public exploit identified as actively used in the wild and EPSS is low at 0.31%.

Technical ContextAI

Langflow is a Python (FastAPI) visual builder for LLM/agent workflows, distributed as the PyPI package langflow (pkg:pip/langflow) and typically self-hosted on port 7860. The flaw lives in langflow/api/v1/endpoints.py, where create_upload_file is declared with only a file and a flow_id UUID path parameter and no authentication dependency and no ownership check - unlike the non-deprecated twin at /api/v1/files/upload/{flow_id}. It calls save_uploaded_file(file, folder_name=flow_id_str), which streams the body to the local filesystem cache without enforcing max_file_size_upload. The CWE-200 (Information Exposure) classification captures the returned absolute file_path (e.g. /Users/ori/Library/Caches/langflow/...), which reveals the OS user, install layout, and cache directory; however the higher-order impact is uncontrolled resource consumption from unbounded writes, which the CVSS vector reflects as A:H.

RemediationAI

Vendor-released patch: upgrade to Langflow 1.9.1 or later, which adds the get_flow dependency (requiring an authenticated user and flow ownership, returning 404 for missing or cross-user flows) and enforces the max_file_size_upload limit with HTTP 413 on the deprecated /api/v1/upload/{flow_id} route (PR #12831). If you cannot upgrade immediately, place Langflow behind an authenticating reverse proxy or network ACL so the /api/v1/upload/ path is not reachable by unauthenticated clients, or block/deny the deprecated POST /api/v1/upload/{flow_id} endpoint at the proxy while permitting the authenticated twin at /api/v1/files/upload/{flow_id}; the trade-off is that any legacy client or SDK caller relying on the deprecated route will break until updated to send an API key. Also apply filesystem quotas or a dedicated cache partition to bound disk-exhaustion damage, and monitor the cache directory growth. Note that even after patching, the response still returns the absolute file_path, so it is disclosed only to the authenticated flow owner. See https://github.com/langflow-ai/langflow/security/advisories/GHSA-x223-p2gf-v735.

More in Python

View all
CVE-2025-24016 CRITICAL POC
9.9 Feb 10

Wazuh SIEM platform versions 4.4.0 through 4.9.0 contain an unsafe deserialization vulnerability in the DistributedAPI t

CVE-2025-27520 CRITICAL POC
9.8 Apr 04

BentoML version 1.4.2 and earlier contains an unauthenticated remote code execution vulnerability through insecure deser

CVE-2025-2945 CRITICAL POC
9.9 Apr 03

pgAdmin 4 contains critical remote code execution vulnerabilities in the Query Tool download and Cloud Deployment endpoi

CVE-2013-5093 MEDIUM POC
6.8 Sep 27

The renderLocalView function in render/views.py in graphite-web in Graphite 0.9.5 through 0.9.10 uses the pickle Python

CVE-2025-32375 CRITICAL POC
9.8 Apr 09

BentoML is a Python library for building online serving systems optimized for AI apps and model inference. Rated critica

CVE-2014-0224 HIGH POC
7.4 Jun 05

OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph

CVE-2024-21644 HIGH POC
7.5 Jan 08

pyLoad download manager version prior to 0.5.0b3.dev77 exposes the Flask SECRET_KEY through an unauthenticated endpoint.

CVE-2026-33017 CRITICAL POC
9.3 Mar 17

Langflow (a visual LLM pipeline builder) contains a critical unauthenticated code execution vulnerability (CVE-2026-3301

CVE-2017-9462 HIGH POC
8.8 Jun 06

In Mercurial before 4.1.3, "hg serve --stdio" allows remote authenticated users to launch the Python debugger, and conse

CVE-2026-49869 CRITICAL POC
10.0 Jun 26

Unauthenticated remote code execution affects Kestra OSS (the open-source event-driven orchestration platform) prior to

CVE-2026-39987 CRITICAL POC
9.3 Apr 08

Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/

CVE-2024-21645 MEDIUM POC
5.3 Jan 08

pyLoad is the free and open-source Download Manager written in pure Python. Rated medium severity (CVSS 5.3), this vulne

Share

EUVD-2026-38511 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy