Answer in brief
CVE-2026-34046 records a High severity (CVSS 8.7) vulnerability in Langflow: Authenticated Users Can Read, Modify, and Delete Any Flow via Missing Ownership Check. The current sources do not mark it as known exploited. The current feed maps langflow-ai/langflow (generic), langflow-ai/langflow-base (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps langflow-ai/langflow (generic), langflow-ai/langflow-base (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:langflow:langflow:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:a:langflow:langflow:1.5.0:dev0:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:a:langflow:langflow:1.5.0:dev1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:a:langflow:langflow-base:*:*:*:*:*:python:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| langflow-ai/langflowgeneric | <1.5.1 | 1.5.1 |
| langflow-ai/langflow-basegeneric | <0.5.1 | 0.5.1 |
Published upstream
Mar 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 28, 2026
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.
Quoted source text, attributed separately from HOL analysis.