llamaCVEVulnerability Intelligence
/
Advisory · GitHub · PyPI · langflow

GHSA-RF6X-R45M-XV3W

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

Parche disponible
Descargar PNG JSON
CVSS
—
high
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versiónPrimer parche a 27 d de la divulgación
Exposición246 dDesde la divulgación, 18 mar 2026, 7:58 a. m.
Detección243 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Parche 1.9.0
Monitoreo
Detectada
18 mar 26
14 abr 26
6 jun 26
17 nov 26
19 nov 26
18 mar 26
19 may 26
19 jul 26
19 sept 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-RF6X-R45M-XV3W divulgada
Remediación Parche 1.9.0 langflow · 27 d desde divulgación
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

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 delete function; (2) In delete_api_key(), verify api_key.user_id == current_user.id before deletion; (3) Raise a 403 Forbidden error if the user doesn't own the key. Example: if api_key.user_id != user_id: raise HTTPException(status_code=403, detail='Unauthorized')

### Notes
Confirmed IDOR vulnerability. The delete_api_key_route endpoint at line 44-53 accepts an api_key_id and calls delete_api_key(db, api_key_id) without passing the current_user. The CRUD function delete_api_key() at crud.py:44-49 retrieves the API key by ID and deletes it without verifying ownership (api_key.user_id == current_user.id). Compare this to the GET endpoint at lines 17-28 which correctly filters by user_id, and the POST endpoint at lines 31-41 which correctly associates the key with user_id. An authenticated attacker can delete any user's API keys by guessing/enumerating UUIDs. Fix: Pass current_user to delete_api_key and verify api_key.user_id == current_user.id before deletion, returning 403 if unauthorized.

### Developer Review Notes
Does not accept current_user as a parameter. Allowing deletion of any user's API keys even without permissions.

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

Versiones

Rangos afectados

Afectada Corregida Última
langflow< 1.9.0
1.9.0
1.13.2
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
pypilangflow
Corregida 1.9.0 27 d 1.13.2 no afectada
Versiones corregidas1.9.0
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Otrahttps://github.com/langflow-ai/langflow/security/advisories/GHSA-rf6x-r45m-xv3w
Otrahttps://github.com/langflow-ai/langflow/commit/fdc1b3b1448ff3317d73d3e769a6c4a1717f74d7
Otrahttps://github.com/langflow-ai/langflow
Otrahttps://github.com/langflow-ai/langflow/releases/tag/1.7.2
Otrahttps://github.com/pypa/advisory-database/tree/main/vulns/langflow/PYSEC-2026-78.yaml

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.