# CVE-2026-33484: Langflow has Unauthenticated IDOR on Image Downloads

> Unauthenticated attackers can download any user's uploaded images by guessing flow IDs, exposing sensitive data in multi-tenant deployments.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-7grx-3xcx-2xv5, PYSEC-2026-80

## What is CVE-2026-33484?

CVE-2026-33484 is a high-severity missing authorization vulnerability in Langflow Langflow, published on 24 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Langflow is a tool for building and deploying AI-powered agents and workflows. In versions 1.0.0 through 1.8.1, the `/api/v1/files/images/{flow_id}/{file_name}` endpoint serves image files without any authentication or ownership check. Any unauthenticated request with a known flow_id and file_name returns the image with HTTP 200. In a multi-tenant deployment, any attacker who can discover or guess a `flow_id` (UUIDs can be leaked through other API responses) can download any user's uploaded images without credentials. Version 1.9.0 contains a patch.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `langflow` | PyPI | From 1.0.0 | 1.9.0 |
| `langflow` | PyPI | From 1.0.0 | 1.9.0 |
| `langflow` | PyPI | From 1.0.0 | 1.9.0 |

Products: Langflow Langflow.

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

Upgrade langflow to 1.9.0 or later.

## Is CVE-2026-33484 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33484 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-33484 and fix it if it is affected.

What it is: CVE-2026-33484 is a high-severity missing authorization vulnerability in Langflow Langflow, published on 24 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33484 exists.

Affected packages and fixed versions:
- langflow (PyPI): affected from 1.0.0; fixed in 1.9.0
- langflow (PyPI): affected from 1.0.0; fixed in 1.9.0
- langflow (PyPI): affected from 1.0.0; fixed in 1.9.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-33484/ (Markdown: https://insights.sbomify.com/CVE-2026-33484/index.md)
```

## Sources

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

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