Is CVE-2026-105698 exploited in the wild?

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

How severe is CVE-2026-105698?

Medium severity, with a CVSS score of 5.4, published 5 October 2026.

Which products and versions are affected?

Langflow 1.0.0 to 1.10.0; Langflow-Base before 0.10.1; langflow (PyPI) >= 1.0.0, < 1.10.1, ECOSYSTEM:introduced=1.0.0,fixed=1.10.1; langflow-base (PyPI) < 0.10.1, ECOSYSTEM:introduced=0,fixed=0.10.1.

Is there a fix for CVE-2026-105698?

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

How is CVE-2026-105698 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-105698?

Check whether you run Langflow, Langflow-Base, langflow (PyPI) or one of the others listed 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-105698: Langflow authorization bypass in flow API endpoints

Q: Is there a fix for CVE-2026-105698?

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

Q: How is CVE-2026-105698 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-105698?

Check whether you run Langflow, Langflow-Base, langflow (PyPI) or one of the others listed 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-105698 · Severity: medium · CVSS 5.4 · Published 2026-10-05

Langflow is a platform for building and deploying AI-powered agents and workflows. Prior to version 1.10.1, the application did not properly verify that a user owns a flow before allowing them to access or execute it via deprecated API endpoints. This could allow an attacker to read private workflow structures, configurations, and execution outputs from other users' flows, potentially triggering unintended side effects.

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

Quick answers

Is CVE-2026-105698 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-105698 being exploited in the wild.
How severe is CVE-2026-105698?: Medium severity, with a CVSS score of 5.4, published 5 October 2026.
Which products and versions are affected?: Langflow 1.0.0 to 1.10.0; Langflow-Base before 0.10.1; langflow (PyPI) >= 1.0.0, < 1.10.1, ECOSYSTEM:introduced=1.0.0,fixed=1.10.1; langflow-base (PyPI) < 0.10.1, ECOSYSTEM:introduced=0,fixed=0.10.1.
Is there a fix for CVE-2026-105698?: Yes. langflow (PyPI): upgrade to 1.10.1 or later; langflow-base (PyPI): upgrade to 0.10.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-105698 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-105698?: Check whether you run Langflow, Langflow-Base, langflow (PyPI) or one of the others listed 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.10.1 or later
```
pip install "langflow>=1.10.1"
```
langflow-base (PyPI): upgrade to 0.10.1 or later
```
pip install "langflow-base>=0.10.1"
```

Technical details

The deprecated POST /api/v1/build/{flow_id}/vertices and POST /api/v1/build/{flow_id}/vertices/{vertex_id} handlers lacked flow ownership verification. In versions up to 1.7.1, these endpoints were unauthenticated and accessible to anyone knowing a flow UUID; from 1.7.2–1.10.0, authentication was required but privilege checks were missing. An attacker could call retrieve_vertices_order to enumerate vertex identifiers and build_vertex to execute selected vertices and extract results, disclosing private flow structure and configured values without modifying stored flows or accessing credential stores.

Affected products

Langflow Langflow 1.0.0 to 1.10.0
Langflow langflow-base before 0.10.1

Identifiers

CVE-2026-105698
GHSA-gh98-4phw-6fmw
PYSEC-2026-4234
PYSEC-2026-4238

Timeline

2026-10-05: disclosed

References

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