# CVE-2026-33053: Langflow has Missing Ownership Verification in API Key Deletion (IDOR)

> Attackers can delete other users' API keys due to missing ownership verification in the deletion endpoint.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-rf6x-r45m-xv3w, PYSEC-2026-78

## What is CVE-2026-33053?

CVE-2026-33053 is a medium-severity missing authorization vulnerability in Langflow Langflow, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Langflow is a tool for building and deploying AI-powered agents and workflows. In versions prior to 1.9.0, the delete_api_key_route() endpoint accepts an api_key_id path parameter and deletes it with only a generic authentication check (get_current_active_user dependency). However, the delete_api_key() CRUD function does NOT verify that the API key belongs to the current user before deletion.

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

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

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


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

Products: Langflow Langflow.

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

Upgrade langflow to 1.9.0 or later.

## Is CVE-2026-33053 being exploited?

There is no known exploitation of CVE-2026-33053 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-33053 and fix it if it is affected.

What it is: CVE-2026-33053 is a medium-severity missing authorization vulnerability in Langflow Langflow, published on 20 Mar 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-33053 in the wild and no public exploit code.

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

## Sources

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

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