| Component | Langflow |
| Severity | high (CVSS 8.8) |
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| Published (NVD) | 2026-03-27 |
| Last modified | 2026-06-17 |
| Affected versions | langflow < 1.5.0 langflow = 1.5.0 langflow = 1.5.0 langflow-base < 0.5.1 |
| Fixed in | 1.5.0, 0.5.1 |
| Weakness | CWE-639CWE-862 |
| CISA KEV | not listed |
NVD 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.
What to do
- Upgrade Langflow to
1.5.0or later (or the patched release of your branch: 0.5.1). - Do not expose the component's API or UI to the internet without authentication in front of it.
Sources
- NVD: CVE-2026-34046
- https://github.com/langflow-ai/langflow/security/advisories/GHSA-8c4j-f57c-35cf
- https://github.com/langflow-ai/langflow/pull/8956
Read more
Other Langflow CVEs
IBM Langflow OSS 1.0.0 through 1.12.2 could allow a remote authenticated attacker to execute arbitrary code due to improper control of code...
IBM Langflow OSS 1.0.0 through 1.12.2 could allow a remote authenticated attacker to execute arbitrary code due to improper control of gener...
IBM Langflow OSS 1.0.0 through 1.12.2 could allow a remote authenticated attacker to obtain sensitive information due to improper limitation...
IBM Langflow OSS 1.0.0 through 1.12.2 could allow a remote attacker to execute arbitrary code due to improper control of code generation.
IBM Langflow OSS 1.0.0 through 1.12.2 could allow a remote authenticated attacker to execute arbitrary code due to improper neutralization o...
IBM Langflow OSS 1.0.0 through 1.12.2 could allow an attacker with access to the server secret and Redis write access to submit a malicious...