Skip to content
AI/ML

CVE-2026-13444

8.1
High
EPSS 0.21%Patch availableJul 31, 2026

Auth bypass in Langflow allows cross-user access and poisoning of Chroma vector collections

common questions

Is CVE-2026-13444 being exploited?

Not confirmed. CVE-2026-13444 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.

How severe is CVE-2026-13444?

CVE-2026-13444 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-13444?

Yes. A fix has been recorded for CVE-2026-13444. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-13444 affect?

CVE-2026-13444 affects IBM Langflow OSS 1.0.0 - 1.10.1, Self-hosted Langflow deployments using Chroma, Chroma vector DB collections using persist_directory/collection_name. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-13444?

Restrict/segregate Chroma persist directories, enforce collection isolation, and apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
IBM Langflow OSS 1.0.0 - 1.10.1Self-hosted Langflow deployments using ChromaChroma vector DB collections using persist_directory/collection_name
impact

Attackers can read other users' private vector documents and insert malicious documents (data exfiltration and collection poisoning) by matching Chroma persist_directory and collection_name.

action required

Patch when possible

affected versions
IBM Langflow OSS
  • affected>= 1.0.0 and <= 1.10.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free