CVE Catalog

CVE-2026-34046

High
Published: Translated: NVD NIST

Summary

Langflow prior to version 1.5.1 had a security vulnerability that allowed authenticated users to access other users' flows without ownership checks. The issue stemmed from the lack of proper query filtering based on the `AUTO_LOGIN` setting.

Risk Assessment

The organization may be exposed to unauthorized access to sensitive data, such as API keys, as well as the ability to modify or delete other users' flows. This poses a risk to data privacy and integrity.

Recommendation

It is recommended to update Langflow to version 1.5.1 or later to eliminate the security vulnerability and ensure proper query filtering. Additionally, conducting a data access audit to identify potential breaches is advisable.

Other vulnerabilities in Langflow

See all
Original NVD description (English source)

Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to version 1.5.1, the `_read_flow` helper in `src/backend/base/langflow/api/v1/flows.py` branched on the `AUTO_LOGIN` setting to decide whether to filter by `user_id`. When `AUTO_LOGIN` was `False` (i.e., authentication was enabled), neither branch enforced an ownership check — the query returned any flow matching the given UUID regardless of who owned it. This allowed any authenticated user to read any other user's flow, including embedded plaintext API keys; modify the logic of another user's AI agents, and/or delete flows belonging to other users. The vulnerability was introduced by the conditional logic that was meant to accommodate public/example flows (those with `user_id = NULL`) under auto-login mode, but inadvertently left the authenticated path without an ownership filter. The fix in version 1.5.1 removes the `AUTO_LOGIN` conditional entirely and unconditionally scopes the query to the reques

Vulnerability data from NVD (NIST) · CISA KEV · EPSS