Is CVE-2026-34046 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-34046 being exploited in the wild.

How severe is CVE-2026-34046?

High severity, with a CVSS score of 8.8, published 27 March 2026.

Which products and versions are affected?

langflow (PyPI) ECOSYSTEM:introduced=0,fixed=1.5.1; langflow-base (PyPI) ECOSYSTEM:introduced=0,fixed=0.5.1.

Is there a fix for CVE-2026-34046?

Yes. langflow (PyPI): upgrade to 1.5.1 or later; langflow-base (PyPI): upgrade to 0.5.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-34046 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-34046?

Check whether you run langflow (PyPI) or langflow-base (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-34046: Langflow authorization bypass in flow management API

CVE-2026-34046 · Severity: high · CVSS 8.8 · Published 2026-03-27

Langflow is a platform used to build and deploy AI-powered agents and workflows. A security flaw allowed any logged-in user to view, modify, or delete the AI workflows created by other users. This could lead to the exposure of sensitive information like API keys, unauthorized changes to AI logic, or the deletion of critical business processes.

Technologies: langflow (PyPI), langflow-base (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-34046 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-34046 being exploited in the wild.
How severe is CVE-2026-34046?: High severity, with a CVSS score of 8.8, published 27 March 2026.
Which products and versions are affected?: langflow (PyPI) ECOSYSTEM:introduced=0,fixed=1.5.1; langflow-base (PyPI) ECOSYSTEM:introduced=0,fixed=0.5.1.
Is there a fix for CVE-2026-34046?: Yes. langflow (PyPI): upgrade to 1.5.1 or later; langflow-base (PyPI): upgrade to 0.5.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-34046 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-34046?: Check whether you run langflow (PyPI) or langflow-base (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

langflow (PyPI): upgrade to 1.5.1 or later
```
pip install "langflow>=1.5.1"
```
langflow-base (PyPI): upgrade to 0.5.1 or later
```
pip install "langflow-base>=0.5.1"
```

Technical details

An Insecure Direct Object Reference (IDOR) vulnerability existed in the `_read_flow` helper function within `src/backend/base/langflow/api/v1/flows.py`. The application branched on the `AUTO_LOGIN` setting but failed to enforce a `user_id` ownership filter when authentication was enabled (`AUTO_LOGIN=False`). Because the GET, PATCH, and DELETE endpoints for flows all rely on this helper, an authenticated attacker could provide a target flow's UUID to bypass authorization. This allowed for the extraction of plaintext API keys embedded in flows, modification of agent logic, or deletion of flows. The issue was resolved in version 1.5.1 by removing the conditional logic and strictly scoping database queries to the requesting user's ID.

Affected products

Langflow AI Langflow < 1.5.1
Langflow AI langflow-base <= 0.5.0

Identifiers

CVE-2026-34046
GHSA-8c4j-f57c-35cf
PYSEC-2026-2567
PYSEC-2026-2570

Timeline

2025-07-09: patched: Pull request merged to fix flow retrieval logic.
2026-03-25: advisory: Vendor security advisory published.
2026-03-27: disclosed: CVE-2026-34046 published.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.