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

Published Oct 5, 2026
·
Updated

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. readresource forwarded the attacker-controlled URI to handlereadresource, which parsed a flowid and filename and called storageservice.getfile 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 handlelistresources and handlelisttools 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.

Affected Software

1 affected component
Langflow Langflow>=1.6.8<1.9.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Langflow to a version that resolves this vulnerability.

    Fixed in 1.9.1

Event History

Oct 5, 2026
CVE Published
via MITRE·08:37 PM
Data Sourced
via MITRE·08:37 PM
DescriptionWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Langflow versions from 1.6.8 up to, but not including, 1.9.1 are affected. The issue applies where an authenticated user can access a project-scoped MCP endpoint.

2

What access does an attacker need?

An attacker needs authenticated access to any project-scoped MCP endpoint. They can then supply a resource URI targeting another user's flow-backed file; no victim interaction is required.

3

What information could be exposed?

The issue can expose uploaded documents, structured data, prompts, and other private artifacts stored for flows in other projects or tenants. It does not allow modification of victim files or stored flows.

4

How could an attacker identify files to target?

Global resource and tool listing behavior could disclose flow and file identifiers, making it easier to construct requests for another user's flow-backed files.

5

What is the remediation?

Upgrade Langflow to version 1.9.1, which fixes the missing authorization check for resource URIs.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203