CVE-2026-105699

Langflow: Authenticated Cross-Project File Disclosure via Unscoped MCP Resource Handlers

Published Oct 5, 2026 CVSS 4.0 · 7.1 High EPSS < 1% KEV · Not listed
Description
Langflow is a tool for building and deploying AI-powered agents and workflows. From 1.6.8 until 1.9.1, Langflow authenticated access to the project identifier in a project-scoped MCP connection but did not authorize the resource URI supplied to resources/read. read_resource forwarded the attacker-controlled URI to handle_read_resource, which parsed a flow_id and filename and called storage_service.get_file without verifying that the flow belonged to the authenticated user or current project. A user with access to any project-scoped MCP endpoint could therefore request another user's flow-backed file, while global handle_list_resources and handle_list_tools behavior could disclose flow and file identifiers that made targeting easier. The vulnerability disclosed uploaded documents, structured data, prompts, and other private flow artifacts across tenants but did not modify victim files or stored flows. This issue is fixed in version 1.9.1.

Analysis

AI-generated

Technical impact

Langflow permitted authenticated users to access file resources that were not bound to their own project. The application accepted a URI for a resource to be read, parsed a flow identifier and filename, and forwarded the request to the storage service without checking that the flow actually belonged to the authenticated user or the current project. This authorization bypass allows the attacker to read any other user’s flow‑backed files, such as uploaded documents, structured data, and prompts, without modifying them. The vulnerability is a classic example of CWE‑639 – Authorization Bypass Through User‑Controlled Key.

Affected Systems

The vulnerability affects Langflow AI’s Langflow application, versions 1.6.8 through 1.9.1. Any deployment running a version in this range that exposes project‑scoped MCP endpoints is vulnerable.

Risk and Exploitability

The CVSS score is 7.1, indicating a high‑severity risk. Although an EPSS score is not available, the flaw is not listed in the CISA KEV catalog. The attack path requires an authenticated user with access to any project‑scoped MCP endpoint, a scenario that is likely to exist in multi‑tenant deployments. Because the vulnerability discloses private flow artifacts, the potential damage to confidentiality is significant, while no integrity or availability impact is noted. The exploit is straightforward for any authenticated user who can specify a target flow ID and filename.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Langflow to version 1.9.1 where the authorization check for read_resource is implemented.
  • Configure your deployment to limit exposure of MCP resource handlers to only those users who require it, or disable them entirely if not needed.
  • Add custom access‑control logic to verify that the flow ID and filename belong to the requesting user or project before serving files, guarding against future regressions.

Generated by OpenCVE AI on October 5, 2026 at 22:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-4hmc-cfm3-w43c Langflow has Authenticated Cross-Project File Disclosure via Unscoped MCP Resource Handlers
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Langflow
Langflow langflow
Vendors & Products Langflow
Langflow langflow
Type Values Removed Values Added
Description Langflow is a tool for building and deploying AI-powered agents and workflows. From 1.6.8 until 1.9.1, Langflow authenticated access to the project identifier in a project-scoped MCP connection but did not authorize the resource URI supplied to resources/read. read_resource forwarded the attacker-controlled URI to handle_read_resource, which parsed a flow_id and filename and called storage_service.get_file without verifying that the flow belonged to the authenticated user or current project. A user with access to any project-scoped MCP endpoint could therefore request another user's flow-backed file, while global handle_list_resources and handle_list_tools behavior could disclose flow and file identifiers that made targeting easier. The vulnerability disclosed uploaded documents, structured data, prompts, and other private flow artifacts across tenants but did not modify victim files or stored flows. This issue is fixed in version 1.9.1.
Title Langflow: Authenticated Cross-Project File Disclosure via Unscoped MCP Resource Handlers
Weaknesses CWE-639
References
Metrics cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 8, 2026, 2:26 AM
Reserved
Oct 5, 2026, 5:48 PM
Status
Undergoing Analysis
Published
Oct 5, 2026, 9:16 PM
Modified
Oct 8, 2026, 3:16 AM