dbcve.org
LangflowApplication

CVE-2026-33053

HIGH · 8.8 CVSS v3.1 Published 2026-03-20
Fix available
A fix is available. Upgrade to 1.9.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in Langflow versions prior to 1.9.0. The delete_api_key_route() endpoint accepts an api_key_id path parameter and requires authentication via get_current_active_user, but the underlying delete_api_key() CRUD function does not verify that the API key belongs to the authenticated user before deletion. This allows any authenticated user to delete any API key in the system by manipulating the api_key_id parameter.

MitigationUpgrade to Langflow version 1.9.0 or later, which includes proper ownership verification in the delete_api_key() function. Until upgrade is possible, implement additional authorization checks at the route level to verify API key ownership before deletion.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LangflowApplication
Affected:< 1.9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Langflow version
    Run 'pip show langflow' or check the package version in your Python environment. Alternatively, check the Langflow startup logs or the installed package metadata.
    Affected if The installed version is below 1.9.0 (e.g., 1.8.0, 1.7.0, etc.)
  2. Verify API key management feature is enabled
    Check if Langflow is configured with authentication enabled and if users can access API key management. Look for evidence of the /api/v1/keys or similar API key routes in your deployed instance.
    Affected if API key management is enabled and users can authenticate to the Langflow API
  3. Confirm the delete_api_key endpoint exists
    Review the Langflow API routes or attempt to access the delete_api_key_route endpoint. In a deployed environment, check the exposed API endpoints for /api/v1/delete-api-key or similar paths.
    Affected if The delete_api_key endpoint is exposed and accessible to authenticated users

You are affected if your Langflow installation is version 1.9.0 or earlier, authentication is enabled, and the API key deletion endpoint is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.0 or later
Fixed in 1.9.0
Interim mitigation

Upgrade to Langflow version 1.9.0 or later, which includes proper ownership verification in the delete_api_key() function. Until upgrade is possible, implement additional authorization checks at the route level to verify API key ownership before deletion.

Recommended fix High confidence

1.9.0

  1. 1. Identify the current Langflow version running in your environment
  2. 2. If using pip/pypi, upgrade to version 1.9.0 or later: pip install langflow --upgrade
  3. 3. If using Docker, pull the fixed image: docker pull langflowai/langflow:1.9.0 (or latest tag)
  4. 4. If using another installation method, obtain Langflow 1.9.0 from the official GitHub releases
  5. 5. Restart the Langflow service after upgrading
  6. 6. Verify the fix works by confirming that authenticated users can no longer delete API keys belonging to other users (should receive 403/authorization error)
Caveat Check Langflow 1.9.0 release notes for any breaking changes; minor version upgrades typically maintain backwards compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Langflow Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33053 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33053 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data