Langflow AI Langflow/Langflow Base Flow Ownership Verification vertices build_graph_from_db_no_cache flow_id access control

Summaryinfo

A vulnerability was found in Langflow AI Langflow and Langflow Base. It has been classified as critical. This affects the function build_graph_from_db_no_cache of the file /api/v1/build/{flow_id}/vertices of the component Flow Ownership Verification. Performing a manipulation of the argument flow_id results in access control. This vulnerability is reported as CVE-2026-105698. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Langflow AI Langflow and Langflow Base (unknown version). It has been classified as critical. This affects the function build_graph_from_db_no_cache of the file /api/v1/build/{flow_id}/vertices of the component Flow Ownership Verification. The manipulation of the argument flow_id with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-105698 since 10/05/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/05/2026). MITRE ATT&CK project uses the attack technique T1068 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Artificial Intelligence Software

Vendor

• Langflow AI

Name

• Langflow
• Langflow Base

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion