IA Squad
SearchPT
python · langflowCritical

Langflow /api/v1/monitor missing ownership checks on 7 endpoints

Langflow's /api/v1/monitor router exposes 7 endpoints that lack ownership checks, allowing any authenticated user to read, modify, rename, or delete another use

17 Jun 2026Read 1 minSeverity: act now

What changed

Langflow's /api/v1/monitor router exposes 7 endpoints that lack ownership checks, allowing any authenticated user to read, modify, rename, or delete another user's messages, sessions, build artifacts, and LLM transaction logs.

Who it affects

All Langflow deployments with multiple users (team instances, SaaS, enterprise self-hosted). Any authenticated user can access other users' data.

What to do today

Apply the ownership check pattern used in GET /monitor/messages (join with Flow and filter by Flow.user_id == current_user.id) to all 7 vulnerable endpoints immediately.

The trail
Collected Audited Written Published