CVE-2026-97678: Langflow: authenticated RCE via improper input validation
HIGHIBM Langflow OSS 1.0.0 through 1.12.2 contains an input validation flaw that lets any authenticated user execute arbitrary code on the server, with a CVSS of 8.8 over the network, low complexity and no user interaction. Exploitation likelihood is currently low: EPSS is 0.00406 (top 67%), the CVE is not in CISA KEV, and there is no public exploit or Nuclei template. Even so, Langflow servers typically hold LLM API keys, vector DB credentials and connectors to internal data, so a low-privilege account is enough to turn into full host compromise and lateral movement. Langflow has a history of RCE flaws that were weaponized quickly, so do not wait for a PoC. Review the IBM advisory (support/pages/node/7290694), upgrade beyond 1.12.2 to the fixed release, and until then restrict access to the Langflow UI/API and audit who holds accounts.
What is the risk?
High. CVSS 8.8 with network vector, low complexity, low privileges and no user interaction, with high impact on confidentiality, integrity and availability. Real-world likelihood is moderate to low today (EPSS 0.00406, not in KEV, no public exploit or scanner template), but the risk rises sharply if the instance is exposed to the internet, allows open self-registration, or shares accounts. The CWE-693 (protection mechanism failure) classification suggests a bypass of a validation or sandboxing control. Package risk data (dependents, Scorecard) is unavailable, so blast radius is not quantified.
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 the fixed version indicated in the IBM advisory (above 1.12.2). 2) Until patched, place Langflow behind a VPN or an authenticating reverse proxy, disable open registration, and remove unnecessary or shared accounts. 3) Run the service as a non-root user in a hardened container with minimal egress and no access to the cloud metadata service. 4) Rotate API keys and secrets stored in Langflow if compromise is suspected, and move secrets to a secrets manager. 5) Detection: monitor for unusual child processes spawned by the Langflow process, unexpected outbound connections, and creation or modification of flows/components by low-privilege users; review API logs for custom component or code validation endpoints being hit abnormally.
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-97678?
IBM Langflow OSS 1.0.0 through 1.12.2 contains an input validation flaw that lets any authenticated user execute arbitrary code on the server, with a CVSS of 8.8 over the network, low complexity and no user interaction. Exploitation likelihood is currently low: EPSS is 0.00406 (top 67%), the CVE is not in CISA KEV, and there is no public exploit or Nuclei template. Even so, Langflow servers typically hold LLM API keys, vector DB credentials and connectors to internal data, so a low-privilege account is enough to turn into full host compromise and lateral movement. Langflow has a history of RCE flaws that were weaponized quickly, so do not wait for a PoC. Review the IBM advisory (support/pages/node/7290694), upgrade beyond 1.12.2 to the fixed release, and until then restrict access to the Langflow UI/API and audit who holds accounts.
Is CVE-2026-97678 actively exploited?
No confirmed active exploitation of CVE-2026-97678 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-97678?
1) Upgrade Langflow OSS to the fixed version indicated in the IBM advisory (above 1.12.2). 2) Until patched, place Langflow behind a VPN or an authenticating reverse proxy, disable open registration, and remove unnecessary or shared accounts. 3) Run the service as a non-root user in a hardened container with minimal egress and no access to the cloud metadata service. 4) Rotate API keys and secrets stored in Langflow if compromise is suspected, and move secrets to a secrets manager. 5) Detection: monitor for unusual child processes spawned by the Langflow process, unexpected outbound connections, and creation or modification of flows/components by low-privilege users; review API logs for custom component or code validation endpoints being hit abnormally.
What systems are affected by CVE-2026-97678?
This vulnerability affects the following AI/ML architecture patterns: agent frameworks, LLM orchestration platforms, RAG pipelines, low-code AI workflow builders.
What is the CVSS score for CVE-2026-97678?
CVE-2026-97678 has a CVSS v3.1 base score of 8.8 (HIGH). The EPSS exploitation probability is 0.57%.
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 low-privilege credentials on an exposed or internally shared Langflow instance (via phishing, credential reuse, or open signup). They send a crafted request to an endpoint that processes user-supplied flow or component input without proper validation, achieving arbitrary code execution on the server. From there they dump environment variables containing LLM and vector DB API keys, install a reverse shell, and move laterally to connected data stores, or silently modify production flows to exfiltrate user prompts and retrieved data.
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