cve.bz

CVE-2026-105699 langflow-ai langflow

7.1 highEPSS 0.4%Fix available

High (7.1) in langflow-ai langflow. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in langflow 1.9.1.

On this page
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.

Severity

CVSS 4.0

7.1 high
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
EPSS
0.4% (unchanged from 0.4% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-16. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • langflow (PyPI): fixed in 1.9.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-105699 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105699?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105699?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105699 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
langflow-ai langflow>= 1.6.8, <= 1.9.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-4hmc-cfm3-w43cPyPIlangflow>=1.6.8 <1.9.11.9.1
PYSEC-2026-4230PyPIlangflow>=1.6.8 <1.9.11.9.1

References

Check your stackJSON