CVE-2026-34046: CWE-639: Authorization Bypass Through User-Controlled Key in langflow-ai langflow
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 requesting user.
AI Analysis
Technical Summary
Langflow versions before 1.5.1 contain an authorization bypass vulnerability (CWE-639, CWE-862) in the _read_flow helper function located in src/backend/base/langflow/api/v1/flows.py. The function's logic branches based on the AUTO_LOGIN setting to decide whether to filter flows by user_id. When AUTO_LOGIN is false (authentication enabled), the code fails to enforce ownership checks, allowing any authenticated user to retrieve flows by UUID regardless of ownership. This permits unauthorized reading, modification, or deletion of other users' flows, potentially exposing sensitive information such as plaintext API keys. The vulnerability was introduced by an attempt to accommodate public/example flows with null user_id under auto-login mode but left the authenticated path unprotected. The fix in version 1.5.1 removes the AUTO_LOGIN conditional and always restricts flow queries to the requesting user.
Potential Impact
An attacker with authenticated access to langflow prior to version 1.5.1 can bypass authorization controls to read, modify, or delete any other user's AI workflow flows. This includes access to sensitive embedded data such as plaintext API keys, which could lead to further compromise of user accounts or services. The vulnerability affects confidentiality, integrity, and availability of user data within langflow.
Mitigation Recommendations
Upgrade langflow to version 1.5.1 or later, where the vulnerability is fixed by unconditionally enforcing user ownership checks on flow queries. There is no indication of vendor advisory content stating 'no action required' or alternative mitigations. Patch status is confirmed by the version update. Users should prioritize updating to the fixed version to prevent unauthorized access to flows.
CVE-2026-34046: CWE-639: Authorization Bypass Through User-Controlled Key in langflow-ai langflow
Description
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 requesting user.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Langflow versions before 1.5.1 contain an authorization bypass vulnerability (CWE-639, CWE-862) in the _read_flow helper function located in src/backend/base/langflow/api/v1/flows.py. The function's logic branches based on the AUTO_LOGIN setting to decide whether to filter flows by user_id. When AUTO_LOGIN is false (authentication enabled), the code fails to enforce ownership checks, allowing any authenticated user to retrieve flows by UUID regardless of ownership. This permits unauthorized reading, modification, or deletion of other users' flows, potentially exposing sensitive information such as plaintext API keys. The vulnerability was introduced by an attempt to accommodate public/example flows with null user_id under auto-login mode but left the authenticated path unprotected. The fix in version 1.5.1 removes the AUTO_LOGIN conditional and always restricts flow queries to the requesting user.
Potential Impact
An attacker with authenticated access to langflow prior to version 1.5.1 can bypass authorization controls to read, modify, or delete any other user's AI workflow flows. This includes access to sensitive embedded data such as plaintext API keys, which could lead to further compromise of user accounts or services. The vulnerability affects confidentiality, integrity, and availability of user data within langflow.
Mitigation Recommendations
Upgrade langflow to version 1.5.1 or later, where the vulnerability is fixed by unconditionally enforcing user ownership checks on flow queries. There is no indication of vendor advisory content stating 'no action required' or alternative mitigations. Patch status is confirmed by the version update. Users should prioritize updating to the fixed version to prevent unauthorized access to flows.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-25T15:29:04.745Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69c6e8bb3c064ed76ff077d0
Added to database: 3/27/2026, 8:29:47 PM
Last enriched: 4/4/2026, 10:49:40 AM
Last updated: 5/11/2026, 5:19:24 AM
Views: 76
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.