GHSA-rf6x-r45m-xv3w: Langflow is Missing Ownership Verification in API Key Deletion (IDOR)

Summary

Langflow's DELETE endpoint for API keys, delete_api_key_route() in src/backend/base/langflow/api/v1/api_key.py, checks only that the caller is authenticated. The delete_api_key() CRUD function in crud.py does not verify that the key belongs to the current user, so any authenticated user can delete other users' API keys by ID. The source says this enables account takeover, denial of service, and disruption of other users' integrations.

Mitigation

Pass current_user to the delete function; in delete_api_key(), verify api_key.user_id == current_user.id before deletion; raise a 403 Forbidden error if the user does not own the key. Example: if api_key.user_id != user_id: raise HTTPException(status_code=403, detail='Unauthorized')

Affected packages in the Exposure Registry

Matched by package name and ecosystem. Each entry shows whether the package delegates to a language model and how many tracked packages depend on it.

• langflowPyPIReaches an LLM package through dependencies

Related items

• MediumCVE-2026-121936: easyVoice server-side request forgery through openaiBaseUrl in /api/v1/ttsSimilar attack · NVD/CVE Database
• MediumCVE-2026-118628: MLflow get-artifacts server-side request forgery information disclosureSimilar attack · NVD/CVE Database
• HighCVE-2026-118625: MLflow Tracking Server privilege escalation via get_endpointsSimilar attack · NVD/CVE Database
• InfoWhen trust becomes the payload: Inside the threats, etc quarterly reportSimilar attack · Elastic Security Labs
• MediumCritical Langflow flaws enable authentication bypass and RCESimilar attack · CSO Online