CVE-2026-97673: Langflow: input validation flaw allows authenticated RCE
HIGHIBM Langflow OSS versions 1.0.0 through 1.12.2 contain an input validation flaw that lets a remote attacker with a low-privilege account execute arbitrary code on the server (CVSS 8.8). Langflow typically holds LLM provider API keys, vector database credentials, and connectors to internal data, so a single compromised instance can expose all of them. Exploitation pressure is currently modest: EPSS is 0.00435 (top 64%), the CVE is not in CISA KEV, and there is no public exploit or Nuclei template. However, the Langflow package has 194 other tracked CVEs and a package risk score of 77/100, which suggests a large, well-studied attack surface that attackers know how to probe. Upgrade to a release newer than 1.12.2 per the IBM advisory, and until you can, restrict Langflow to trusted networks and review who holds accounts on it.
What is the risk?
High. The CVSS vector (AV:N/AC:L/PR:L/UI:N) means any network-reachable instance is exposed to anyone holding a valid account, and exploitation needs no user interaction. Confidentiality, integrity, and availability impact are all rated high. Likelihood is moderated by the authentication requirement, the low EPSS score (0.00435), no KEV listing, and no known public exploit. The risk rises sharply for instances with open self-registration, shared or weak credentials, or internet exposure. The package has a heavy CVE history (194 other CVEs), which raises the odds that a working exploit emerges. The CWE classification (CWE-693, protection mechanism failure) is generic and says little about the exact flaw.
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 newer than 1.12.2 as directed in the IBM advisory (https://www.ibm.com/support/pages/node/7290694); no patched version is listed in the structured data, so confirm the fixed release with IBM. 2) Until patched, take instances off the public internet and place them behind a VPN, SSO proxy, or IP allowlist. 3) Disable open self-registration, audit existing accounts, remove unused users, and rotate weak credentials. 4) Run Langflow in a container or VM with least-privilege IAM, no host mounts, and egress filtering. 5) Rotate API keys and secrets stored in Langflow if compromise is suspected. 6) Detect anomalies by monitoring for unexpected child processes spawned by the Langflow process, unusual outbound connections, and new or modified flows or custom components from low-privilege accounts.
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-97673?
IBM Langflow OSS versions 1.0.0 through 1.12.2 contain an input validation flaw that lets a remote attacker with a low-privilege account execute arbitrary code on the server (CVSS 8.8). Langflow typically holds LLM provider API keys, vector database credentials, and connectors to internal data, so a single compromised instance can expose all of them. Exploitation pressure is currently modest: EPSS is 0.00435 (top 64%), the CVE is not in CISA KEV, and there is no public exploit or Nuclei template. However, the Langflow package has 194 other tracked CVEs and a package risk score of 77/100, which suggests a large, well-studied attack surface that attackers know how to probe. Upgrade to a release newer than 1.12.2 per the IBM advisory, and until you can, restrict Langflow to trusted networks and review who holds accounts on it.
Is CVE-2026-97673 actively exploited?
No confirmed active exploitation of CVE-2026-97673 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-97673?
1) Upgrade Langflow OSS to a version newer than 1.12.2 as directed in the IBM advisory (https://www.ibm.com/support/pages/node/7290694); no patched version is listed in the structured data, so confirm the fixed release with IBM. 2) Until patched, take instances off the public internet and place them behind a VPN, SSO proxy, or IP allowlist. 3) Disable open self-registration, audit existing accounts, remove unused users, and rotate weak credentials. 4) Run Langflow in a container or VM with least-privilege IAM, no host mounts, and egress filtering. 5) Rotate API keys and secrets stored in Langflow if compromise is suspected. 6) Detect anomalies by monitoring for unexpected child processes spawned by the Langflow process, unusual outbound connections, and new or modified flows or custom components from low-privilege accounts.
What systems are affected by CVE-2026-97673?
This vulnerability affects the following AI/ML architecture patterns: LLM orchestration frameworks, agent frameworks, RAG pipelines, visual workflow builders, vector database integrations.
What is the CVSS score for CVE-2026-97673?
CVE-2026-97673 has a CVSS v3.1 base score of 8.8 (HIGH). The EPSS exploitation probability is 0.61%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0012Valid AccountsAML.T0049Exploit Public-Facing ApplicationAML.T0050Command and Scripting InterpreterCompliance 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 execute arbitrary code due to improper input validation.
Exploitation Scenario
An attacker obtains a low-privilege Langflow account through credential stuffing, an exposed sign-up page, or a phished developer login. They send crafted input to the vulnerable endpoint, which the application fails to validate properly, and gain code execution as the Langflow service user. From there they read environment variables and the database to harvest LLM provider keys and vector store credentials, then plant a malicious component in a shared flow to persist. Finally they exfiltrate data from connected knowledge bases or pivot into the internal network.
Weaknesses (CWE)
CWE-693 — Protection Mechanism Failure: The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HReferences
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