GHSA-9c59-2mvc-vfr8: Langflow: IDOR/BOLA in Monitor API — Missing Ownership Enforcement on 7 Endpoints

Summary

Langflow's `/api/v1/monitor` router exposes seven endpoints that read, modify, rename or delete user-owned messages, sessions, build artifacts and LLM transaction logs without checking that the requester owns the target. Any authenticated user can act on another user's data by supplying a resource ID or `flow_id`, which is an IDOR/BOLA flaw. The source notes that `GET /monitor/messages` in the same file enforces ownership correctly, so the pattern existed but was applied inconsistently. The PoC was tested on Langflow v1.7.3.

Mitigation

The source does not state a fix yet. Check the original advisory for updates.

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