Langflow is vulnerable to information disclosure due to cross-user MCP tool cache collision and incomplete secret scrubbing on public flows

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps IBM/Langflow OSS (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for IBM/Langflow OSS.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 4, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 4, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 4, 2026

Sources and claim methodology

• Source referenceibm.com

Related CVEs

• Langflow OSS is affected by arbitrary file read due to path traversal vulnerabilities in file and knowledge base componentsSame ibm/langflow oss package
• Langflow OSS is affected by arbitrary file read due to path traversal vulnerabilities in file and knowledge base componentsSame ibm/langflow oss package
• Langflow is affected by improper authorization due to missing access control on the voice-mode WebSocket endpointSame ibm/langflow oss package
• Langflow OSS is affected by server-side request forgery due to missing URL validation in flow componentsSame ibm/langflow oss package
• IBM ContextForge MCP Gateway is affected by credential disclosure and privilege escalation via jq filter executionAlso CWE-200
• Security vulnerabilities have been addressed in IBM Verify Identity Access and IBM Security Verify AccessSame generic ecosystem