Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Authenticated low-priv network access (PR:L) with low complexity yields high confidentiality (reading private docs) and high integrity (collection pollution); no availability impact and scope unchanged.
Primary rating from Vendor (ibm).
CVSS VectorVendor: ibm
Lifecycle Timeline
3DescriptionCVE.org
IBM Langflow OSS 1.0.0 through 1.10.1 can allow an attacker to access another user's private vector documents by creating their own flow with matching Chroma persist_directory and collection_name values. The attacker receives exact victim content in their workflow output despite having no authorization to read the victim's flow. Additionally, the attacker can pollute the victim's collection by inserting their own documents into the shared namespace.
AnalysisAI
Cross-tenant vector document disclosure in IBM Langflow OSS 1.0.0 through 1.10.1 lets an authenticated low-privilege user read another user's private Chroma-backed documents by building a flow that reuses the victim's persist_directory and collection_name, returning exact victim content in the attacker's workflow output. The same shared-namespace flaw also lets the attacker write their own documents into the victim's collection, corrupting its integrity. No public exploit is identified at time of analysis and CISA SSVC rates exploitation as none, but the CVSS 8.1 rating reflects the combined high confidentiality and integrity impact.
Technical ContextAI
Langflow is an open-source visual/low-code framework for building LLM and retrieval-augmented-generation (RAG) pipelines, where Chroma is a commonly used embedded vector database. Chroma persists collections to a local path defined by persist_directory and identifies logical document sets by collection_name. In affected Langflow versions those two values act as a shared global namespace: any flow specifying matching values binds to the same underlying Chroma store regardless of which user owns the original flow. Because Langflow does not scope Chroma access to the owning user or flow, isolation between tenants collapses. This maps to CWE-520 (misconfiguration/failure to enforce the intended security boundary), with the practical root cause being missing per-user access control on a shared storage namespace rather than any memory-safety defect.
RemediationAI
Patch available per vendor advisory: upgrade IBM Langflow OSS to the fixed release described in IBM's advisory at https://www.ibm.com/support/pages/node/7279989 (no exact fixed version number is stated in the provided data, so confirm the target version directly from that advisory). Until patched, avoid sharing or reusing Chroma persist_directory and collection_name values across users, and assign each user or flow a unique, non-guessable collection_name and an isolated persist_directory path so distinct tenants cannot bind to the same store; the trade-off is added configuration overhead and loss of any intentional cross-flow collection sharing. In multi-tenant or hosted environments, restrict who can create or edit flows and consider isolating each tenant's Langflow instance and Chroma storage at the filesystem or container level, accepting the higher operational cost of per-tenant isolation.
More in Langflow Oss
View allUnauthenticated remote code execution in IBM Langflow OSS versions 1.0.0 through 1.10.0 lets any network-reachable attac
Authenticated command injection in IBM Langflow OSS 1.0.0 through 1.11.1 lets any logged-in flow user escalate to arbitr
Code injection in IBM Langflow OSS versions 1.0.0 through 1.10.0 lets an authenticated user execute arbitrary operating-
Remote code execution in IBM Langflow OSS 1.0.0 through 1.11.1 allows a network-accessible authenticated attacker with l
Authentication bypass in IBM Langflow OSS 1.0.0 through 1.10.0 lets an unauthenticated remote attacker retrieve a long-l
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.11.5 allows an unauthenticated remote attacker to run
Remote OS command execution in IBM Langflow OSS (versions 1.0.0 through 1.11.5) lets remote attackers run arbitrary oper
Unauthenticated remote code execution in IBM Langflow OSS versions 1.0.0 through 1.9.3 allows attackers to fully comprom
Arbitrary Python code execution in IBM Langflow OSS 1.0.0 through 1.10.0 (Langflow versions up to 1.9.2) allows authenti
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.0 allows attackers to run arbitrary code by planting a mali
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.10.0 lets any logged-in user run arbitrary Pytho
Arbitrary file write in IBM Langflow OSS 1.0.0 through 1.10.0 lets an attacker who controls an external HTTP server plan
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-51272
GHSA-vrqm-44rp-59j5