Read the docs

Langflow build endpoints expose other users' flows and vertex results

Priority MEDIUM 58CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-639.

Summary

Langflow from 1.0.0 before 1.10.1 and langflow-base before 0.10.1 do not check flow ownership in the deprecated POST /api/v1/build/{flow_id}/vertices handlers. An authenticated user who knows another user's flow UUID can load the private graph and run selected vertices to read their results (CWE-639). Versions through 1.7.1 need no login. This discloses private flow structure, configured values and selected outputs, and can trigger the victim's configured side effects.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00225 13th percentileScored 2026-11-07
Fix Fixed langflow (langflow-ai): 1.10.1langflow-base (langflow-ai): 0.10.1+2 more products

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Langflowlangflow1.0.0 to before 1.10.11.10.1Patch availableCNA
Langflowlangflow-basebefore 0.10.10.10.1Patch availableCNA
—langflow (PyPI)1.0.0 to before 1.10.11.10.1Patch availableGHSA-gh98-4phw-6fmw
—langflow-base (PyPI)before 0.10.10.10.1Patch availableGHSA-gh98-4phw-6fmw
  • langflow VendorLangflow Affected 1.0.0 to before 1.10.1 Fixed in 1.10.1 Patch available CNA
  • langflow-base VendorLangflow Affected before 0.10.1 Fixed in 0.10.1 Patch available CNA
  • langflow (PyPI) Vendor— Affected 1.0.0 to before 1.10.1 Fixed in 1.10.1 Patch available GHSA-gh98-4phw-6fmw
  • langflow-base (PyPI) Vendor— Affected before 0.10.1 Fixed in 0.10.1 Patch available GHSA-gh98-4phw-6fmw

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:langflow:langflow:*:*:*:*:*:*:*:*——Langflow
  • cpe:2.3:a:langflow:langflow:*:*:*:*:*:*:*:* Versions — — ·Langflow

Remediation

Upgrade langflow to version 1.10.1 and langflow-base to version 0.10.1, which fix the issue.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

  • Fix · CNA langflow (langflow-ai) Fixed in 1.10.1
  • Fix · CNA langflow-base (langflow-ai) Fixed in 0.10.1
  • Fix · GHSA-gh98-4phw-6fmw langflow (PyPI) Fixed in 1.10.1 Advisory →
  • Fix · GHSA-gh98-4phw-6fmw langflow-base (PyPI) Fixed in 0.10.1 Advisory →

Timeline

  1. 2026-10-06 Threatist record created from CVE-2026-105698
  2. 2026-10-06 CISA SSVC decision points changed
  3. 2026-10-07 Alias added: GHSA-gh98-4phw-6fmw
  4. 2026-10-07 Fix available: PyPI/[email protected], PyPI/[email protected] · GHSA-gh98-4phw-6fmw
  5. 2026-10-07 CVSS score added · GHSA-gh98-4phw-6fmw
  6. 2026-10-07 Weakness changed · GHSA-gh98-4phw-6fmw
  7. 2026-10-07 6 new references · GHSA-gh98-4phw-6fmw

References

  • TI-2026-08085 Unauthenticated Remote Code Execution via Auto-Login Bypass and Code Validation KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-00553 Langflow exec_globals Inclusion of Functionality from Untrusted Control Sphere Remote… KEVCVSS 3.0CRITICAL 9.8
  • TI-2025-24427 Langflow <= 1.6.9 CORS Misconfiguration to Token Hijack & RCE KEVCVSS 4.0CRITICAL 9.4
  • TI-2025-02845 Langflow < 1.3.0 Unauthenticated RCE via /api/v1/validate/code KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-25463 Langflow has Unauthenticated Remote Code Execution via Public Flow Build Endpoint KEVCVSS 4.0CRITICAL 9.3
  • TI-2026-39928 Authorization bypass in langflow KEVCVSS 3.1HIGH 8.4
See all 236 →

Sources