CVE-2026-13444 IBM CVE debrief

Who should care

Langflow instance administrators and users with exposure to untrusted users should assess and remediate affected instances. Defenders should verify and remediate affected Langflow instances, especially those exposed to untrusted users, to prevent exploitation and data compromise. Security teams and vulnerability management teams should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Why it matters

CVE-2026-13444 allows unauthorized access to private vector documents in Langflow OSS instances, enabling data exposure and pollution. Defenders should verify and remediate affected instances, especially those exposed to untrusted users, to prevent exploitation and data compromise.

• Unauthorized access to sensitive user data
• Potential data pollution through document insertion
• Need for verification of affected instances and user exposure
• Priority for remediation to prevent exploitation

Technical summary

The vulnerability allows an attacker to access another user's private vector documents by creating a flow with matching Chroma persist_directory and collection_name values, receiving exact victim content in their workflow output without authorization. This enables data exposure and pollution. Defenders should prioritize verifying and remediating affected Langflow instances, especially those exposed to untrusted users. The vulnerability affects Langflow OSS 1.0.0 through 1.10.1 and can be remediated by updating to version 1.10.2 or later.

Defensive priority

Defenders should prioritize verifying and remediating affected Langflow instances, especially those exposed to untrusted users.

Recommended defensive actions

• Verify Langflow instance version and exposure to untrusted users
• Remediate affected instances to version 1.10.2 or later
• Monitor for suspicious workflow activity and document insertions
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. Defenders should verify Langflow instance version and exposure to untrusted users, and review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. The vulnerability allows unauthorized access to private vector documents, enabling data exposure and pollution. Affected instances should be remediated to version 1.10.2 or later.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.