Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Langflow user credentials
-
DeliveryAccess Langflow web interface
-
ExploitNavigate to pipeline LambdaFilterComponent
-
ExecutionInject malicious Python code in filter expression
-
PersistTrigger filter evaluation
-
ImpactExecute arbitrary code in Langflow process context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Authentication is required: the attacker must possess valid Langflow login credentials (PR:L). The attacker must have access to the LambdaFilterComponent in Langflow's pipeline builder or configuration interface. The lambda filter expression input field must not validate or sanitize Python code before passing it to the eval() function. Default Langflow installations with the LambdaFilterComponent enabled and network-accessible are vulnerable; air-gapped or restricted deployments with disabled lambda filters are not affected. The vulnerability does not require user interaction beyond the attacker's own actions (UI:N). |
| Impact | CVSS 6.3 with AV:N/AC:L/PR:L indicates remote network-accessible exploitation requiring valid user credentials but low attack complexity. EPSS is not provided, limiting probabilistic exploitation assessment. The public availability of exploit code significantly increases practical risk despite the CVSS score being in the medium range. The KEV (Known Exploited Vulnerability) status is not confirmed in provided data, but public exploit availability combined with active vulnerability disclosure indicates real-world exploitation potential. The PR:L (low privilege) requirement means legitimate Langflow users, external collaborators, or compromised low-privilege accounts can exploit this. Attack complexity is low (AC:L), suggesting no special exploitation techniques are required beyond crafting malicious lambda filter expressions. The confidentiality, integrity, and availability impacts are all rated as low (C:L/I:L/A:L), but code injection in Python typically enables privilege escalation and full system compromise depending on Langflow's runtime environment and permissions. The unpatched status and vendor non-responsiveness elevate practical risk significantly. |
| Exploit ScenarioDerived | An authenticated Langflow user with access to pipeline configuration navigates to the Lambda Filter component and enters a malicious Python expression such as '__import__("os").system("id")' in the filter field. When the filter is executed or evaluated, the injected code runs within the Langflow process's context, allowing the attacker to read files, execute system commands, or pivot to other systems depending on Langflow's runtime permissions. Publicly available exploit code reduces the barrier for non-expert attackers. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 03, 2026
Code injection via the eval function in Langflow's LambdaFilterComponent allows remote authenticated attackers to execute arbitrary code with low-to-medium integrity and confidentiality impact. The vulnerability affects Langflow up to version 1.8.4, requires user login (PR:L), and has publicly available exploit code. The vendor did not respond to early disclosure notification.
RemediationAI
Upgrade Langflow to a version newer than 1.8.4 once a patched release is available; however, no vendor-released patch version is identified in provided data. Immediate compensating controls should include: (1) Restrict network access to Langflow deployments using firewall rules or VPN-only access, reducing exposure to remote attackers despite PR:L requirement; (2) Disable or remove the LambdaFilterComponent from the Langflow UI if the lambda filter feature is not in use, eliminating the attack surface; (3) Implement strict input validation on lambda filter expressions by intercepting and sanitizing filter parameters before they reach the eval function (requires code modification if no configuration option exists); (4) Run Langflow with minimal Python privileges and in isolated environments (containers, dedicated user accounts) to limit impact if code injection succeeds; (5) Monitor and audit lambda filter usage for suspicious patterns. Contact langflow-ai for patch availability and timeline given their non-response to disclosure.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in pypi
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability exists in the LambdaFilterComponent's eval function (src/lfx/src/lfx/components/llm_operations/lambda_filter.p) which improperly handles user-supplied input without adequate sanitization or sandboxing. The weakness is classified as CWE-94 (Code Injection), a class of flaws where untrusted data is passed to an interpreter or evaluator function without proper validation. In Python and similar languages, eval() functions execute arbitrary code with full interpreter privileges. Langflow's Lambda filter component likely uses Python's eval() or similar constructs to process filter expressions, allowing attackers who can craft malicious input through the Langflow interface to break out of intended code execution boundaries.
Know when Langflow gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Primary rating from Vendor (VulDB) · only source for this CVE.
CVSS VectorVendor: VulDB
Lifecycle Timeline
4DescriptionCVE.org
A weakness has been identified in langflow-ai langflow up to 1.8.4. This affects the function eval of the file src/lfx/src/lfx/components/llm_operations/lambda_filter.p of the component LambdaFilterComponent. Executing a manipulation can lead to code injection. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Langflow before 1.3.0 allows unauthenticated remote code injection through the /api/v1/validate/code endpoint, enabling
Langflow has a third RCE vulnerability via exec_globals (EPSS 10.0%) allowing inclusion of untrusted code that executes
Account takeover and remote code execution in Langflow AI workflow platform versions ≤1.6.9 due to a CORS misconfigurati
Langflow has a code injection vulnerability in the code component (EPSS 2.6%) enabling remote code execution through the
Langflow has an eval injection in eval_custom_component_code (EPSS 2.0%) enabling remote code execution through crafted
Remote code execution in IBM Langflow OSS 1.0.0 through 1.9.3 lets an unauthenticated attacker inject and run arbitrary
Code injection in Langflow CSV Agent node before 1.8.0. The node hardcodes allow_dangerous_code=True, enabling arbitrary
Langflow through 0.6.19 allows remote code execution if untrusted users are able to reach the "POST /api/v1/custom_compo
OS command injection in Langflow's MCP stdio transport allows an attacker who can reach the MCP server configuration end
langflow <=1.0.18 is vulnerable to Remote Code Execution (RCE) as any component provided the code functionality and the
langflow v1.0.12 was discovered to contain a remote code execution (RCE) vulnerability via the PythonCodeTool component.
Langflow before 1.7.0.dev45 exposes multiple API endpoints without authentication, allowing unauthenticated access to us
EUVD-2026-26838
GHSA-9fpm-3445-2vx4
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB