Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

GHSA-x223-p2gf-v735 — langflow

CRITICALFix: langflow-ai/langflow#12831

GHSA-x223-p2gf-v735 is a critical-severity (CVSS 9.3) Information Exposure vulnerability in langflow. A fix is available for langflow — see the affected versions and patch details below.

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

Also known asCVE-2026-55450PYSEC-2026-224
Published
Jun 17, 2026
Updated
Jun 26, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-x223-p2gf-v735.

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-x223-p2gf-v735 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
🐍langflow

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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/):

@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:

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

Example:

# 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 Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIlangflowall versions1.9.1pip install --upgrade 'langflow==1.9.1'

Affected Products

1 product · 1 configurations
Application
langflowlangflow
< 1.9.1
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for langflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update langflow to 1.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x223-p2gf-v735 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

How to detect GHSA-x223-p2gf-v735

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-x223-p2gf-v735 -u https://target
Template
Langflow < 1.9.1 - Unauthenticated File Upload
Severity
critical
Impact
Unauthenticated attackers can exhaust server storage and gain information about file paths, potentially aiding further attacks.
Remediation
Update to version 1.9.1 or later.

Template by ProjectDiscovery nuclei-templates (xtr0nix), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### 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=HTTP
O3 Security · Impact-Aware SCA

Is GHSA-x223-p2gf-v735 in your dependencies?

Find it across PyPI, including transitive dependencies.

GHSA-x223-p2gf-v735: langflow (Critical 9.3) | O3 Security