CVE-2026-33053

Langflow has Missing Ownership Verification in API Key Deletion (IDOR)

Published Mar 20, 2026 CVSS 4.0 · 6.1 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability originates from the delete_api_key_route() endpoint in Langflow, which accepts an api_key_id parameter but only performs a generic authentication check. The underlying delete_api_key() function then deletes the key without confirming that it belongs to the requesting user. As a result, any authenticated user can delete any API key in the system, potentially denying access to other users' services and disrupting the operation of applications that rely on those keys. This is an instance of the CWE-639 "Authorization Bypass Using Privileged Credentials" weakness, and the effect is a loss of availability for services tied to the deleted keys.

Affected Systems

Langflow‑ai‘s Langflow product versions prior to 1.9.0 are affected. All releases before 1.9.0 that include the unverified delete_api_key_route() endpoint are vulnerable. Users of 1.9.0 and later can be considered safe from this issue.

Risk and Exploitability

With a CVSS score of 6.1, the vulnerability is classified as moderate severity. The EPSS score is less than 1 %, indicating a low probability of exploitation, and the vulnerability is not listed in CISA’s KEV catalog. An attacker must first authenticate to the application, but once logged in they can craft a request to the delete endpoint with any api_key_id value, making the attack fairly straightforward for a legitimate user or anyone who has obtained valid credentials. The lack of ownership verification removes a critical access control check, raising the risk for accidental or intentional service disruption.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Langflow version 1.9.0 or newer to eliminate the missing ownership verification bug.
  • If an upgrade cannot be performed immediately, configure your deployment to restrict or disable the delete API key endpoint for non‑administrative users.
  • Monitor logs for unusual or repetitive deletion attempts of API keys, especially those issued to other users.

Generated by OpenCVE AI on March 20, 2026 at 20:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-rf6x-r45m-xv3w Langflow is Missing Ownership Verification in API Key Deletion (IDOR)
History
Type Values Removed Values Added
CPEs cpe:2.3:a:langflow:langflow:*:*:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Langflow
Langflow langflow
Vendors & Products Langflow
Langflow langflow
Type Values Removed Values Added
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.
Title Langflow has Missing Ownership Verification in API Key Deletion (IDOR)
Weaknesses CWE-639
References
Metrics cvssV4_0

{'score': 6.1, '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'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 20, 2026, 6:07 PM
Reserved
Mar 17, 2026, 6:10 PM
Status
Analyzed
Published
Mar 20, 2026, 7:16 AM
Modified
Jun 17, 2026, 10:36 AM