# CVE-2026-9225: Langflow is vulnerable to unauthorized file system access due to path traversal and missing storage path validation

> Authenticated attackers can read other users' files via path traversal in the File/Read component, exposing sensitive data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-v63q-2gxx-5p2w

## What is CVE-2026-9225?

CVE-2026-9225 is a medium-severity path traversal vulnerability in Langflow Langflow, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Langflow OSS 1.0.0 through 1.11.5 Langflow could allow an authenticated attacker to access sensitive files belonging to other users due to improper access control in the File/Read File component. When executing flows through the /api/v1/run/advanced/{flow_id} endpoint, the application allows component inputs to reference storage paths using arbitrary user or flow identifiers without verifying ownership. An attacker with low‑privileged authenticated access can supply a crafted file path pointing to another user’s storage namespace, causing the backend to read and return the contents of files uploaded by other users. This vulnerability bypasses intended authorization checks enforced by the file management API and may result in unauthorized disclosure of sensitive user data.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Langflow Langflow.

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

No fix has been published for CVE-2026-9225 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9225 being exploited?

There is no known exploitation of CVE-2026-9225 in the wild and no public exploit code.

## 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-9225 and fix it if it is affected.

What it is: CVE-2026-9225 is a medium-severity path traversal vulnerability in Langflow Langflow, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9225 in the wild and no public exploit code.

Affected product: Langflow Langflow. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-9225/ (Markdown: https://insights.sbomify.com/CVE-2026-9225/index.md)
```

## Sources

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

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