Quick answers
- Is CVE-2026-33053 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-33053 being exploited in the wild.
- How severe is CVE-2026-33053?
- High severity, with a CVSS score of 4, published 18 March 2026.
- Which products and versions are affected?
- langflow (PyPI) ECOSYSTEM:introduced=0,fixed=1.9.0.
- Is there a fix for CVE-2026-33053?
- Yes. langflow (PyPI): upgrade to 1.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-33053 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-33053?
- Check whether you run langflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- langflow (PyPI): upgrade to 1.9.0 or later
pip install "langflow>=1.9.0"
Technical details
An Insecure Direct Object Reference (IDOR) vulnerability exists in the `delete_api_key_route` endpoint within `src/backend/base/langflow/api/v1/api_key.py`. The endpoint accepts an `api_key_id` (UUID) and performs a generic authentication check but fails to verify if the authenticated user owns the specific key being deleted. An attacker with a valid account can exploit this by sending a DELETE request with a targeted `api_key_id`, leading to unauthorized deletion of credentials. This issue was addressed in version 1.9.0 by ensuring the `current_user` is passed to the CRUD function to verify ownership before proceeding with the deletion.
Affected products
- langflow-ai langflow < 1.9.0
Identifiers
- CVE-2026-33053
- GHSA-rf6x-r45m-xv3w
- PYSEC-2026-78
Timeline
- 2026-03-16: disclosed
- 2026-03-18: advisory: GitHub Advisory published
- 2026-03-20: other: NVD published