GHSA-X223-P2GF-V735
Vulnerability from github – Published: 2026-06-17 18:43 – Updated: 2026-06-17 18:43Summary
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
- Space exhaustion on server that can lead to Denial-of-Service.
- 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": [
{
"package": {
"ecosystem": "PyPI",
"name": "langflow"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.9.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-55450"
],
"database_specific": {
"cwe_ids": [
"CWE-200",
"CWE-306",
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2026-06-17T18:43:12Z",
"nvd_published_at": null,
"severity": "CRITICAL"
},
"details": "### Summary\nUnauthenticated users can upload any amount of data to the server without any limitations. No need for any prior knowledge, only network access to Langflow.\n\nThis can lead to space exhaustion on the server.\n\nIn 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.\n\nTested on commit 2d67402b1dbaefcbce85a244d4a6cd5e4bda1cfe\n\n### Details\nCode is in `langflow/api/v1/[endpoints.py](http://endpoints.py/)`:\n```python\n@router.post(\n \"/upload/{flow_id}\",\n status_code=HTTPStatus.CREATED,\n deprecated=True,\n)\nasync def create_upload_file(\n file: UploadFile,\n flow_id: UUID,\n) -\u003e UploadFileResponse:\n...\n```\nAs can be seen above, there is no authentication. There is not validation over `flow_id` as well, unlike other endpoints:\n```\n flow_id_str = str(flow_id)\n file_path = await asyncio.to_thread(save_uploaded_file, file, folder_name=flow_id_str)\n```\nFunction `save_uploaded_file` saves the file to local file-system.\nSuggested fix:\n1. Add authentication to route.\n2. Only return relative path or filename.\n\n### PoC\nPoC:\n```bash\ncurl \u0027http://localhost:7860/api/v1/upload/\u003cany_uuid\u003e\u0027 -F \"file=@\u003cany_file\u003e\"\n```\n\nExample:\n```bash\n# curl \u0027http://localhost:7860/api/v1/upload/11111111-1111-1111-1111-111111111111\u0027 -F \"file=@/tmp/dummy.txt\"\n{\"flowId\":\"11111111-1111-1111-1111-111111111111\",\"file_path\":\"/Users/ori/Library/Caches/langflow/11111111-1111-1111-1111-111111111111/9d63c3b5b7623d1fa3dc7fd1547313b9546c6d0fbbb6773a420613b7a17995c8.txt\"}\n```\n\n### Impact\n1. Space exhaustion on server that can lead to Denial-of-Service.\n2. Information leak - leakage of absolute path of langflow\u0027s cache directory in server.\n\n\n\n\n\n### Patches\nFixed in **1.9.1** via PR [#12831](https://github.com/langflow-ai/langflow/pull/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`) \u2014 closing the unauthenticated upload and disk-exhaustion vectors. Upgrade to **1.9.1 or later**.\n\nNote: the response still returns the file\u0027s absolute path (`file_path`); after this fix it is only disclosed to the authenticated owner of the flow.\n\n\nOri Lahav\nSecurity Researcher @ Rubrik Inc.",
"id": "GHSA-x223-p2gf-v735",
"modified": "2026-06-17T18:43:12Z",
"published": "2026-06-17T18:43:12Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/langflow-ai/langflow/security/advisories/GHSA-x223-p2gf-v735"
},
{
"type": "WEB",
"url": "https://github.com/langflow-ai/langflow/pull/12831"
},
{
"type": "PACKAGE",
"url": "https://github.com/langflow-ai/langflow"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "Langflow: Unauthenticated file upload leads to DoS (space exhaustion) and information leak"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.