CVE-2026-110192: Langflow: weak credential protection exposes secrets

MEDIUM

Published October 29, 2026

CISO Take

CVE-2026-110192 is an information disclosure flaw (CWE-522, insufficiently protected credentials) in IBM Langflow OSS 1.0.0 through 1.12.8 that lets any authenticated user with low privileges read sensitive credentials over the network. Langflow typically stores API keys for LLM providers, vector databases and third-party tools, so a single low-privilege account can become a path to every downstream service the flows touch. Exploitation likelihood looks limited today: it is not in CISA KEV, no public exploit or Nuclei template exists, and no EPSS score has been published yet, but the attack is low complexity and needs no user interaction. Upgrade to the fixed release listed in IBM's advisory (node 7294467), rotate any API keys and secrets stored in Langflow, and restrict account creation on exposed instances.

Sources:NVDibm.comATLAS

What is the risk?

Medium (CVSS 6.5) with high confidentiality impact and no integrity or availability impact. Exploitation requires a valid account, which lowers risk for tightly controlled internal deployments. Risk rises for multi-user or internet-exposed instances with open sign-up, shared workspaces, or many stored provider credentials. No KEV listing, public exploit, scanner template, or EPSS data was available at publication, so real-world exploitation is currently unconfirmed. The exact credential exposure path is not detailed in the available data.

How does the attack unfold?

Initial Access

Attacker gains a low-privilege authenticated Langflow account over the network.

AML.T0012

Credential Access

Attacker retrieves insufficiently protected credentials stored by Langflow.

AML.T0055

Impact

Stolen LLM provider and vector DB keys enable unauthorized model usage, data access, and lateral movement.

AML.T0083

Initial Access

Attacker gains a low-privilege authenticated Langflow account over the network.

AML.T0012

Credential Access

Attacker retrieves insufficiently protected credentials stored by Langflow.

AML.T0055

Impact

Stolen LLM provider and vector DB keys enable unauthorized model usage, data access, and lateral movement.

AML.T0083

What systems are affected?

Package	Ecosystem	Vulnerable Range	Patched
Langflow	pip	—	No patch
156.0KPushed 6d ago18% patched~66d to patchFull package profile →

Do you use Langflow? You're affected.

How severe is it?

CVSS 3.1

6.5 / 10

EPSS

0.2%

chance of exploitation in 30 days

Higher than 16% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

No known exploitation

Sophistication

Trivial

What is the attack surface?

AVNetwork

ACLow

PRLow

UINone

SUnchanged

CHigh

INone

ANone

What should I do?

6 steps

Upgrade Langflow OSS to the fixed version specified in the IBM advisory (https://www.ibm.com/support/pages/node/7294467).
Rotate all API keys, tokens, and secrets stored in or accessible to Langflow, prioritizing LLM provider and vector DB credentials.
Disable open registration, enforce SSO or strong authentication, and review accounts holding low-privilege access.
Move secrets to an external secrets manager with least-privilege scopes rather than storing them in flows.
Restrict network exposure of Langflow to trusted networks or a VPN.
Audit access logs for unusual credential or variable reads and monitor provider-side usage for anomalous API key activity.

How is it classified?

Data LeakageData ExtractionFrameworkAPIAML.T0012- Valid Accounts AML.T0055- Unsecured Credentials AML.T0083- Credentials from AI Agent Configuration

Which compliance frameworks are affected?

This CVE is relevant to:

EU AI Act

Article 15-Accuracy, robustness and cybersecurity

ISO 42001

A.7.4-Security of AI system components and data

NIST AI RMF

MANAGE 2.3-Respond to and recover from unknown risks and AI incidents

OWASP LLM Top 10

LLM02-Sensitive Information Disclosure

Frequently Asked Questions

What is CVE-2026-110192?

Is CVE-2026-110192 actively exploited?

No confirmed active exploitation of CVE-2026-110192 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-110192?

1. Upgrade Langflow OSS to the fixed version specified in the IBM advisory (https://www.ibm.com/support/pages/node/7294467). 2. Rotate all API keys, tokens, and secrets stored in or accessible to Langflow, prioritizing LLM provider and vector DB credentials. 3. Disable open registration, enforce SSO or strong authentication, and review accounts holding low-privilege access. 4. Move secrets to an external secrets manager with least-privilege scopes rather than storing them in flows. 5. Restrict network exposure of Langflow to trusted networks or a VPN. 6. Audit access logs for unusual credential or variable reads and monitor provider-side usage for anomalous API key activity.

What systems are affected by CVE-2026-110192?

This vulnerability affects the following AI/ML architecture patterns: agent frameworks, RAG pipelines, LLM workflow orchestration, vector databases.

What is the CVSS score for CVE-2026-110192?

CVE-2026-110192 has a CVSS v3.1 base score of 6.5 (MEDIUM). The EPSS exploitation probability is 0.25%.

What is the AI security impact?

Affected AI Architectures

agent frameworksRAG pipelinesLLM workflow orchestrationvector databases

MITRE ATLAS Techniques

AML.T0012Valid Accounts

AML.T0055Unsecured Credentials

AML.T0083Credentials from AI Agent Configuration

Compliance Controls Affected

EU AI Act: Article 15

ISO 42001: A.7.4

NIST AI RMF: MANAGE 2.3

OWASP LLM Top 10: LLM02

What are the technical details?

Original Advisory

IBM Langflow OSS 1.0.0 through 1.12.8 could allow a remote authenticated attacker to obtain sensitive information due to insufficiently protected credentials.

Exploitation Scenario

An attacker obtains a low-privilege Langflow account, for example through an open sign-up, a phished user, or a reused password. They query the vulnerable endpoint or interface that returns credentials insufficiently protected, retrieving stored LLM provider keys and vector database tokens. The attacker then uses those keys directly against the providers to run unauthorized inference, pull indexed proprietary data from the RAG store, or pivot into connected internal services, all without further interaction with Langflow.

Weaknesses (CWE)

CWE-522Insufficiently Protected CredentialsPrimary CWE-522Insufficiently Protected Credentials

CWE-522 — Insufficiently Protected Credentials: The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

[Architecture and Design] Use an appropriate security mechanism to protect the credentials.
[Architecture and Design] Make appropriate use of cryptography to protect the credentials.

Source: MITRE CWE corpus.