Affected: langflow-ai langflow

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.

Affected: PyPI: langflow

**Detection Method:** Kolega.dev Deep Code Scan

| Attribute | Value | |---|---| | Location | src/backend/base/langflow/api/v1/api_key.py:44-53 | | Practical Exploitability | High | | Developer Approver | faizan@kolega.ai |

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

### Affected Code ``` @router.delete("/{api_key_id}", dependencies=[Depends(auth_utils.get_current_active_user)]) async def delete_api_key_route( api_key_id: UUID, db: DbSession, ): try: await delete_api_key(db, api_key_id) except Exception as e: raise HTTPException(status_code=400, detail=str(e)) from e return {"detail": "API Key deleted"} ```

### Evidence In crud.py lines 44-49, delete_api_key() retrieves the API key by ID and deletes it without checking if the key belongs to the authenticated user. The endpoint also doesn't pass the current_user to the delete function for verification.

### Impact An authenticated attacker can enumerate and delete API keys belonging to other users by guessing or discovering their API key IDs. This allows account takeover, denial of service, and disruption of other users' integrations.

### Recommendation Modify the delete_api_key endpoint and function: (1) Pass current_user to the…