Langflow OSS: Improper Neutralization of Directives in Dynamically Evaluated Code
CVE-2026-19295 is a critical-severity improper neutralization of directives in dynamically evaluated code vulnerability in Langflow OSS from IBM, with a CVSS 3.1 base score of 9.9 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected Langflow OSS versions: 1.0.0 through 1.11.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.55% chance of exploitation within 30 days, higher than 76% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Langflow to 1.11.2 or a later version.
- Read the advisory on ibm.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| IBM | Langflow OSS | 1.0.0 through 1.11.1 | Not stated |
| Langflow | Langflow | 1.0.0 up to, but not including, 1.11.2 | 1.11.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (us.ibm.com).
Official description
IBM Langflow OSS 1.0.0 through 1.11.1 allows an authenticated attacker to execute arbitrary operating system commands in the server process by saving a flow with a crafted type field value and triggering a build of a wrapper flow that references it. This allowed privilege escalation from "authenticated flow user" to arbitrary OS-level command execution under the server process identity, bypassing the LANGFLOW_ALLOW_CUSTOM_COMPONENTS=false policy control.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Directives in Dynamically Evaluated Code
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. eval).
How developers prevent this class of flaw
- If possible, refactor your code so that it does not need to use eval() at all.
- For Python programs, it is frequently encouraged to use the ast.literal_eval() function instead of eval, since it is intentionally designed to avoid executing code. However, an adversary could still cause excessive memory or stack consumption via deeply nested structures, so the python documentation discourages use of ast.literal_eval() on untrusted data.
More Improper Neutralization of Directives in Dynamically Evaluated Code vulnerabilities (CWE-95)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Langflow OSS
- 8.1 High severity
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
Recent Improper Neutralization of Directives in Dynamically Evaluated Code vulnerabilities
- 9.8 Critical severity
- 9.2 Critical severity
- 10.0 Critical severity
- 9.9 Critical severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.