langflow-ai · Langflow · published 2026-03-27
CVE-2026-34046Langflow: Authenticated Users Can Read, Modify, and Delete Any Flow via Missing Ownership Check
Routine No exploitation evidence; EPSS 0.5%.
CVE-2026-34046 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 42% of all CVEs. This Langflow vulnerability: CVSS 8.7 (v4.0), a successful attack gives total control of the component. Fixed upstream in Langflow 1.5.1, 0.5.1. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Langflow 1.5.1, 0.5.1.
Patch events
AI toolingLangflow
Langflow security releases: 1.5.1, 0.5.1
Upgrade to
1.5.10.5.1Why: Vendor security release for server software (most severe: CVE-2026-34046).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.5% (43th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.7 (v4.0)CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- langflow-ai langflow
< 1.5.1(affected)
- langflow-ai langflow-base
< 0.5.1(affected)
Description (from the CVE record)#
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 from the CVE Program record.