# CVE-2026-105698: Langflow: Cross-user flow access and vertex execution via deprecated /api/v1/build/{flow_id}/vertices endpoints

> Attackers can access private AI workflows and execute vertices without proper ownership checks, leading to data disclosure and unauthorized code execution.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-gh98-4phw-6fmw, PYSEC-2026-4234, PYSEC-2026-4238

## What is CVE-2026-105698?

CVE-2026-105698 is a medium-severity missing authorization vulnerability in langflow-ai langflow, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Langflow is a tool for building and deploying AI-powered agents and workflows. From 1.0.0 until 1.10.1, Langflow did not verify flow ownership in the deprecated POST /api/v1/build/{flow_id}/vertices and POST /api/v1/build/{flow_id}/vertices/{vertex_id} handlers. Through version 1.7.1, an unauthenticated caller who knew another user's flow UUID could reach these handlers; from version 1.7.2 through 1.10.0, callers had to authenticate but needed no elevated privileges. Such a caller could cause retrieve_vertices_order to load and cache the private graph, enumerate its vertex identifiers, and use build_vertex to execute selected vertices and receive their results. build_graph_from_db_no_cache performed a primary-key lookup without an owner filter. This could disclose private flow structure, configured values, and selected outputs and could trigger victim-configured side effects and build-history records, although it did not expose the victim's variable-store credentials or permit modification of the stored flow. This issue is fixed in Langflow 1.10.1 and langflow-base 0.10.1.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-105698?

6 open source packages ship an affected version, including langflow and langflow-base.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `langflow` | PyPI | From 1.0.0 | 1.10.1 |
| `langflow` | PyPI | From 1.0.0 | 1.10.1 |
| `langflow` | PyPI | From 1.0.0 | 1.10.1 |
| `langflow-base` | PyPI | All versions | 0.10.1 |
| `langflow-base` | PyPI | All versions | 0.10.1 |
| `langflow-base` | PyPI | All versions | 0.10.1 |

## How do I fix CVE-2026-105698?

Upgrade langflow to 1.10.1 or later.

## Is CVE-2026-105698 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105698 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105698 and fix it if it is affected.

What it is: CVE-2026-105698 is a medium-severity missing authorization vulnerability in langflow-ai langflow, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105698 exists.

Affected packages and fixed versions:
- langflow (PyPI): affected from 1.0.0; fixed in 1.10.1
- langflow (PyPI): affected from 1.0.0; fixed in 1.10.1
- langflow (PyPI): affected from 1.0.0; fixed in 1.10.1
- langflow-base (PyPI): affected all versions; fixed in 0.10.1
- langflow-base (PyPI): affected all versions; fixed in 0.10.1
- langflow-base (PyPI): affected all versions; fixed in 0.10.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105698/ (Markdown: https://insights.sbomify.com/CVE-2026-105698/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105698
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105698
- OSV: https://osv.dev/vulnerability/CVE-2026-105698

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105698/
Summaries are generated and may contain mistakes; the official description above is the record.