VulnerabilityPublished 30 Jul 2026

CVE-2026-13444: 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

Affects langflowSource GCVE Database

Compare

Authoritative record:CVE-2026-13444· High 8.1

Not known to be exploited · CVSS 8.1 High.

Data as of 29 Oct 2026, 07:15 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-vrqm-44rp-59j5

What to do

Affected software

Product	Affected	Fixed in
PyPIlangflow`pkg:pypi/langflow`Other threats	Affected =1.0.0 <=1.10.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is available, restrict flow creation privileges to trusted users only to limit exploitation potential. Monitor for any updates from IBM regarding patches or official mitigations for this vulnerability.

Description

IBM Langflow OSS versions 1.0.0 through 1.10.1 have a vulnerability that allows an attacker with limited privileges to access another user's private vector documents by creating a flow with matching Chroma persist_directory and collection_name values. This unauthorized access exposes the victim's exact content in the attacker's workflow output. Additionally, the attacker can insert documents into the victim's collection, potentially polluting the victim's data. The vulnerability does not require user interaction but does require some level of privilege to create flows.

Impact

An attacker with the ability to create flows can access confidential vector documents of other users without authorization, leading to a high confidentiality breach. The attacker can also modify the victim's collection by adding documents, causing data integrity issues. There is no impact on availability. This compromises both confidentiality and integrity of user data within the affected versions of IBM Langflow OSS.

Summary

The vulnerability in IBM Langflow OSS 1.0.0 through 1.10.1 (CVE-2026-13444) arises from insufficient access controls on vector document collections identified by Chroma persist_directory and collection_name parameters. An attacker who can create their own flow with these matching parameters can read private vector documents belonging to other users and inject documents into the victim's collection namespace. This leads to unauthorized disclosure and integrity compromise of victim data. The CVSS 3.1 vector indicates network attack vector, low attack complexity, low privileges required, no user interaction, unchanged scope, and high confidentiality and integrity impact with no availability impact.

CWE-520.NET Misconfiguration: Use of Impersonation (opens in a new tab)
Variant weaknessOWASP Top 10 A05:2021: Security Misconfiguration (opens in a new tab)
Allowing a .NET application to run at potentially escalated levels of access to the underlying operating and file systems can be dangerous and result in various forms of attacks.
Operation
Run the application with limited privilege to the underlying operating and file system.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Jul 2026, 23:33 UTC

WeaknessesCWE-520

Technical details

References

Community reviews

Related threats