# CVE-2026-48520: Langflow: Unauthenticated Shareable Playground arbitrary local or S3 file read

> Attackers can read arbitrary local or S3 files by manipulating file paths in public Langflow playground executions.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-rcjh-r59h-gq37, PYSEC-2026-244

## What is CVE-2026-48520?

CVE-2026-48520 is a medium-severity path traversal vulnerability in Langflow Langflow, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to 1.10.0, the "Shareable Playground" (or "Public Flows" in code) contains a potential arbitrary file-read vulnerability, depending on the exact flow configuration used. By making a flow public, public execution of the flow is allowed. The execution request can contain a list of files that gets read by Langflow and fed into the LLM. The files path can be any path supported by the storage - it can be either a local file or S3 path if supported by the local configuration This vulnerability is fixed in 1.10.0.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2026-48520?

3 open source packages ship an affected version, including langflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `langflow` | PyPI | All versions | 1.10.0 |
| `langflow` | PyPI | All versions | 1.10.0 |
| `langflow` | PyPI | All versions | 1.10.0 |

Products: Langflow Langflow.

## How do I fix CVE-2026-48520?

Upgrade langflow to 1.10.0 or later.

## Is CVE-2026-48520 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48520 exists.

## Other vulnerabilities in Langflow Langflow

- [CVE-2026-9198](https://insights.sbomify.com/CVE-2026-9198/): IBM Langflow Code Injection (critical 9.8, exploited in the wild)
- [CVE-2026-0770](https://insights.sbomify.com/CVE-2026-0770/): Langflow Inclusion of Functionality from Untrusted Control Sphere (critical 9.8, exploited in the wild)
- [CVE-2025-3248](https://insights.sbomify.com/CVE-2025-3248/): Langflow Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2025-34291](https://insights.sbomify.com/CVE-2025-34291/): Langflow Origin Validation Error (critical 9.4, exploited in the wild)
- [CVE-2026-33017](https://insights.sbomify.com/CVE-2026-33017/): Langflow Code Injection (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48520 and fix it if it is affected.

What it is: CVE-2026-48520 is a medium-severity path traversal vulnerability in Langflow Langflow, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48520 exists.

Affected packages and fixed versions:
- langflow (PyPI): affected all versions; fixed in 1.10.0
- langflow (PyPI): affected all versions; fixed in 1.10.0
- langflow (PyPI): affected all versions; fixed in 1.10.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48520/ (Markdown: https://insights.sbomify.com/CVE-2026-48520/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48520
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48520
- OSV: https://osv.dev/vulnerability/CVE-2026-48520

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48520/
Summaries are generated and may contain mistakes; the official description above is the record.