CVE-2026-93677: Langflow: info disclosure lets authed users read sensitive data
MEDIUMCVE-2026-93677 is an information exposure flaw (CWE-200) in IBM's Langflow OSS 1.0.0 through 1.12.2 that lets any low-privileged authenticated user over the network read sensitive data they should not see. The scope-changed CVSS vector (S:C, C:H) signals that the leak crosses a security boundary, which in Langflow deployments typically means stored API keys, model provider credentials, or other users' flows and variables. Near-term exploitation risk is moderate to low: EPSS is 0.46% (62nd percentile), the CVE is not in CISA KEV, and there is no public exploit or Nuclei template, but Langflow has 194 other CVEs and a 77/100 package risk score, so it is a well-scrutinized and historically attacked target. Upgrade beyond 1.12.2 per the IBM advisory (https://www.ibm.com/support/pages/node/7290694), restrict Langflow to trusted networks and users, and rotate any credentials stored in Langflow if untrusted users had accounts.
What is the risk?
Medium-high. The CVSS score of 7.7 reflects low attack complexity, network reach, no user interaction, and high confidentiality impact with changed scope. Exploitation requires a valid account, which lowers exposure for single-tenant or internal deployments but matters for multi-user or self-registration setups. Real-world exploitation likelihood is currently low (EPSS 0.0046, no KEV listing, no public exploit or scanner template). The patched version is not stated in the structured data, so confirm it in the IBM advisory. The package's history of 194 CVEs raises the likelihood that researchers and attackers will probe this area.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| Langflow | pip | — | No patch |
Do you use Langflow? You're affected.
How severe is it?
What is the attack surface?
What should I do?
1 step1) Upgrade Langflow OSS to a version later than 1.12.2 as directed by the IBM advisory at https://www.ibm.com/support/pages/node/7290694. 2) Until patched, limit access to trusted users, disable open self-registration, and keep instances off the public internet or behind SSO/VPN. 3) Rotate LLM provider keys, vector DB credentials, and any secrets stored in Langflow variables or flows if untrusted accounts have had access. 4) Move secrets to an external secrets manager rather than storing them in flow definitions. 5) Review Langflow API access logs for unusual enumeration or bulk reads by low-privileged accounts, and monitor provider usage for anomalous API key use.
What does CISA's SSVC say?
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-93677?
CVE-2026-93677 is an information exposure flaw (CWE-200) in IBM's Langflow OSS 1.0.0 through 1.12.2 that lets any low-privileged authenticated user over the network read sensitive data they should not see. The scope-changed CVSS vector (S:C, C:H) signals that the leak crosses a security boundary, which in Langflow deployments typically means stored API keys, model provider credentials, or other users' flows and variables. Near-term exploitation risk is moderate to low: EPSS is 0.46% (62nd percentile), the CVE is not in CISA KEV, and there is no public exploit or Nuclei template, but Langflow has 194 other CVEs and a 77/100 package risk score, so it is a well-scrutinized and historically attacked target. Upgrade beyond 1.12.2 per the IBM advisory (https://www.ibm.com/support/pages/node/7290694), restrict Langflow to trusted networks and users, and rotate any credentials stored in Langflow if untrusted users had accounts.
Is CVE-2026-93677 actively exploited?
No confirmed active exploitation of CVE-2026-93677 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-93677?
1) Upgrade Langflow OSS to a version later than 1.12.2 as directed by the IBM advisory at https://www.ibm.com/support/pages/node/7290694. 2) Until patched, limit access to trusted users, disable open self-registration, and keep instances off the public internet or behind SSO/VPN. 3) Rotate LLM provider keys, vector DB credentials, and any secrets stored in Langflow variables or flows if untrusted accounts have had access. 4) Move secrets to an external secrets manager rather than storing them in flow definitions. 5) Review Langflow API access logs for unusual enumeration or bulk reads by low-privileged accounts, and monitor provider usage for anomalous API key use.
What systems are affected by CVE-2026-93677?
This vulnerability affects the following AI/ML architecture patterns: agent frameworks, LLM workflow orchestration, RAG pipelines, multi-tenant LLM platforms.
What is the CVSS score for CVE-2026-93677?
CVE-2026-93677 has a CVSS v3.1 base score of 6.5 (MEDIUM). The EPSS exploitation probability is 0.32%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0012Valid AccountsAML.T0036Data from Information RepositoriesAML.T0055Unsecured CredentialsCompliance Controls Affected
What are the technical details?
Original Advisory
IBM Langflow OSS 1.0.0 through 1.12.2 could allow a remote authenticated attacker to obtain sensitive information due to exposure of sensitive information to an unauthorized actor.
Exploitation Scenario
An attacker obtains or registers a low-privileged account on an internet-reachable or shared Langflow instance. They call the vulnerable API endpoint over the network and retrieve sensitive information they are not authorized to see, such as stored API keys, connection strings, or other users' flow configurations. They then use the harvested provider keys to access the organization's LLM accounts and vector databases, or to run up costs and extract proprietary data. The specific vulnerable endpoint is not disclosed in the public data, so this scenario is inferred from the CWE-200 classification and the scope-changed CVSS vector.
Weaknesses (CWE)
CWE-200Exposure of Sensitive Information to an Unauthorized ActorPrimaryCWE-200Exposure of Sensitive Information to an Unauthorized ActorCWE-200 — Exposure of Sensitive Information to an Unauthorized Actor: The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
- [Architecture and Design] Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NReferences
Timeline
Related Vulnerabilities
CVE-2026-1056110.0Langflow: auth bypass + unauthenticated RCE (CVSS 10)
Same package: langflowCVE-2026-1013410.0Langflow: unauthenticated RCE via tool_code injection
Same package: langflowCVE-2026-333099.9langflow: Path Traversal enables file access
Same package: langflowCVE-2026-552559.9Langflow: IDOR allows cross-user flow execution
Same package: langflowCVE-2026-78739.9Langflow: authenticated RCE enables credential theft
Same package: langflow