<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/cve-2026-34046-broken-authorization-in-langflow-exposes-user-flows-lflrzxv7j" -->

---
title: CVE-2026-34046: Broken authorization in Langflow exposes...
description: Dynatrace Security Researchers discovered CVE-2026-34046, a high-severity broken authorization vulnerability (CVSS 8.7) in Langflow affecting versions up to...
canonical: https://daily.dev/posts/cve-2026-34046-broken-authorization-in-langflow-exposes-user-flows-lflrzxv7j
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: CVE-2026-34046: Broken authorization in Langflow exposes user flows | daily.dev
og:description: Dynatrace Security Researchers discovered CVE-2026-34046, a high-severity broken authorization vulnerability (CVSS 8.7) in Langflow affecting versions up to...
og:url: https://daily.dev/posts/cve-2026-34046-broken-authorization-in-langflow-exposes-user-flows-lflrzxv7j
og:image: https://api.daily.dev/og/posts/LfLRzXv7j.png
og:image:alt: CVE-2026-34046: Broken authorization in Langflow exposes user flows
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# CVE-2026-34046: Broken authorization in Langflow exposes user flows

**[Dynatrace](https://daily.dev/sources/dynatrace)** · 5 min read · 1 upvotes · 0 comments

## Summary

Dynatrace Security Researchers discovered CVE-2026-34046, a high-severity broken authorization vulnerability (CVSS 8.7) in Langflow affecting versions up to and including 1.5.0. The flaw resides in the `_read_flow` helper function in the flow management API: when `AUTO_LOGIN` is disabled (i.e., authentication is active), no ownership check is enforced, allowing any authenticated user to read, modify, or delete flows belonging to other users by knowing or guessing a flow UUID. Since Langflow flows often contain embedded API keys and proprietary agent logic, unauthorized read access carries serious consequences. The vulnerability was reported to maintainers on July 8, 2025, fixed the next day but initially disguised as an internal refactor, and formally published as a CVE on March 27, 2026. Remediation requires upgrading to langflow >= 1.5.1 and langflow-base >= 0.5.1.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.dynatrace.com/news/blog/cve-2026-34046-broken-authorization-in-langflow-exposes-user-flows>

## Questions this post answers

### What is CVE-2026-34046 and how does it affect Langflow?

CVE-2026-34046 is a high severity (CVSS 8.7) broken authorization vulnerability in Langflow's flow management API. The root cause is in the _read_flow function, which only enforced an ownership check when AUTO_LOGIN was enabled. With authentication active, any logged-in user could read, modify, or delete other users' flows by knowing or guessing a flow UUID, exposing embedded API keys and proprietary agent logic.

_Teams tracking AI framework vulnerabilities like this Langflow flaw can follow disclosures on daily.dev._

### Which Langflow versions are vulnerable to CVE-2026-34046 and how do I fix it?

Langflow versions up to and including 1.5.0, and langflow-base up to and including 0.5.0, are affected. Upgrade to langflow 1.5.1 or later and langflow-base 0.5.1 or later to remediate the broken authorization issue in the flow management API's ownership check logic.

_Developers patching agentic AI dependencies can track Langflow updates like this on daily.dev._

### How long did it take for Langflow to disclose the authorization vulnerability after being reported?

The vulnerability was reported to Langflow maintainers on July 8, 2025, and a fix was committed the next day, July 9, 2025. However, the fix was listed as an internal refactor rather than a security fix, and the formal advisory and CVE publication (CVE-2026-34046) did not occur until March 27, 2026, months later.

_Security teams weighing disclosure timing risks can follow vulnerability writeups like this on daily.dev._

## Similar posts on daily.dev

- [Critical Langflow Path Traversal Flaw Exploited for Unauthenticated RCE](https://daily.dev/posts/critical-langflow-path-traversal-flaw-exploited-for-unauthenticated-rce-fuqzjitk7) · Orca Security Blog · 0 upvotes · 0 comments
- [Path traversal flaw in AI dev platform Langflow exploited in attacks](https://daily.dev/posts/path-traversal-flaw-in-ai-dev-platform-langflow-exploited-in-attacks-spteyrcl6) · BleepingComputer · 0 upvotes · 0 comments
- [Langflow RCE under active attack months after a patch was shipped](https://daily.dev/posts/langflow-rce-under-active-attack-months-after-a-patch-was-shipped-jzjannqnb) · CSO Online · 0 upvotes · 0 comments
- [Critical Langflow Vulnerability Allows Remote Code Execution](https://daily.dev/posts/critical-langflow-vulnerability-allows-remote-code-execution-vnn8uugk6) · AI Cyber Insights · 1 upvotes · 0 comments
- [Critical Flaw in Langflow AI Platform Under Attack](https://daily.dev/posts/critical-flaw-in-langflow-ai-platform-under-attack-fz5dbqsfo) · Dark Reading · 0 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#appsec](https://daily.dev/tags/appsec), [#agentic-ai](https://daily.dev/tags/agentic-ai)

[View this post on daily.dev](https://daily.dev/posts/cve-2026-34046-broken-authorization-in-langflow-exposes-user-flows-lflrzxv7j)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"CVE-2026-34046: Broken authorization in Langflow exposes user flows","url":"https://daily.dev/posts/cve-2026-34046-broken-authorization-in-langflow-exposes-user-flows-lflrzxv7j","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/cve-2026-34046-broken-authorization-in-langflow-exposes-user-flows-lflrzxv7j"},"datePublished":"2026-08-07T17:32:54.750Z","dateModified":"2026-09-14T06:28:39.355Z","description":"Dynatrace Security Researchers discovered CVE-2026-34046, a high-severity broken authorization vulnerability (CVSS 8.7) in Langflow affecting versions up to...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/145269837d4134823b75e49fe6dba176?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/145269837d4134823b75e49fe6dba176?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Dynatrace","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Dynatrace","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/3ca5a9897e9748f4a39fa9736389609e","url":"https://daily.dev/sources/dynatrace"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/cve-2026-34046-broken-authorization-in-langflow-exposes-user-flows-lflrzxv7j","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,appsec,agentic-ai","timeRequired":"PT5M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Dynatrace","item":"https://daily.dev/sources/dynatrace"},{"@type":"ListItem","position":3,"name":"CVE-2026-34046: Broken authorization in Langflow exposes user flows"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/cve-2026-34046-broken-authorization-in-langflow-exposes-user-flows-lflrzxv7j#faq","mainEntity":[{"@type":"Question","name":"What is CVE-2026-34046 and how does it affect Langflow?","acceptedAnswer":{"@type":"Answer","text":"CVE-2026-34046 is a high severity (CVSS 8.7) broken authorization vulnerability in Langflow's flow management API. The root cause is in the _read_flow function, which only enforced an ownership check when AUTO_LOGIN was enabled. With authentication active, any logged-in user could read, modify, or delete other users' flows by knowing or guessing a flow UUID, exposing embedded API keys and proprietary agent logic. Teams tracking AI framework vulnerabilities like this Langflow flaw can follow disclosures on daily.dev."}},{"@type":"Question","name":"Which Langflow versions are vulnerable to CVE-2026-34046 and how do I fix it?","acceptedAnswer":{"@type":"Answer","text":"Langflow versions up to and including 1.5.0, and langflow-base up to and including 0.5.0, are affected. Upgrade to langflow 1.5.1 or later and langflow-base 0.5.1 or later to remediate the broken authorization issue in the flow management API's ownership check logic. Developers patching agentic AI dependencies can track Langflow updates like this on daily.dev."}},{"@type":"Question","name":"How long did it take for Langflow to disclose the authorization vulnerability after being reported?","acceptedAnswer":{"@type":"Answer","text":"The vulnerability was reported to Langflow maintainers on July 8, 2025, and a fix was committed the next day, July 9, 2025. However, the fix was listed as an internal refactor rather than a security fix, and the formal advisory and CVE publication (CVE-2026-34046) did not occur until March 27, 2026, months later. Security teams weighing disclosure timing risks can follow vulnerability writeups like this on daily.dev."}}]}
```

