Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to langflow instance
-
DeliverySend crafted HTTP request to MCP API
-
ExploitInject code via X-Forwarded-For header
-
ExecutionVulnerable get_client_ip function processes header
-
PersistCode executed in backend context
-
ImpactArbitrary code execution
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Input neutralization, injection prevention
|
| Exploitation Conditions | Exploitation requires PR:L (authenticated access) - the attacker must possess valid credentials to access the langflow instance and reach the Model Context Protocol Configuration API endpoints. The X-Forwarded-For header manipulation is the injection vector and requires no special client-side configuration beyond crafting an HTTP request with a malicious header value. Default langflow deployments are vulnerable if authentication is enabled but not sufficiently restricted; air-gapped or internally-deployed instances with limited user access are less exposed. The vulnerability is triggered when the install_mcp_config function processes MCP configuration requests that include user-controlled or forwarded client IP information. |
| Impact | CVSS 6.3 with vector AV:N/AC:L/PR:L indicates authenticated network-based access with low attack complexity and limited impact (confidentiality, integrity, availability). The presence of publicly available exploit code (POC=YES) combined with no KEV listing suggests real-world risk exists but exploitation appears targeted or still emerging rather than widespread automated campaigns. EPSS data is not provided, limiting probabilistic assessment. The E:P flag indicates exploit is probable, while RL:W (Workaround) and RC:R (Reasonable) suggest mitigations exist and confidence in reproducibility is moderate. The critical limitation is the PR:L (Privilege Level: Low) requirement - exploitation requires authenticated access to the langflow instance, significantly reducing attack surface compared to unauthenticated vulnerabilities. For organizations with public-facing langflow deployments or untrusted user populations, this poses material risk; for internal-only deployments with limited user access, risk is lower. The lack of vendor response to disclosure raises concern about patch timeline and availability. |
| Exploit ScenarioDerived | An authenticated user with access to a langflow instance crafts an HTTP request to the Model Context Protocol Configuration API (install_mcp_config endpoint) with a malicious X-Forwarded-For header containing Python code injection payloads. The vulnerable get_client_ip function extracts and processes this header without sanitization, passing it downstream where it is evaluated in an unsafe context. The injected code executes within the langflow backend process, potentially allowing the attacker to read sensitive configuration data, modify workflows, or escalate privileges depending on the execution context. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 20, 2026
Code injection in langflow-ai langflow up to version 1.8.3 allows authenticated remote attackers to execute arbitrary code via manipulation of the X-Forwarded-For HTTP header in the Model Context Protocol Configuration API endpoint. The vulnerability affects the get_client_ip function in src/backend/base/langflow/api/v1/mcp_projects.py and has publicly available exploit code; the vendor did not respond to early disclosure notification.
RemediationAI
Upgrade langflow to a version released after 1.8.3 that includes a patch for the X-Forwarded-For header injection vulnerability; however, no specific patched version is confirmed in available data due to lack of vendor response. Organizations unable to upgrade immediately should implement network-level controls: disable or restrict access to the Model Context Protocol Configuration API endpoints (specifically the install_mcp_config function in src/backend/base/langflow/api/v1/mcp_projects.py) by limiting IP ranges or requiring VPN access. Additionally, configure web application firewalls to sanitize or block X-Forwarded-For headers containing suspicious characters or code patterns, or remove X-Forwarded-For headers entirely if the reverse proxy configuration does not legitimately require this header. Monitor API logs for unusual X-Forwarded-For values. Note that WAF filtering is a temporary measure and does not address the root cause; patching remains the primary remediation.
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 resides in the Model Context Protocol (MCP) Configuration API component of langflow, specifically in the get_client_ip and install_mcp_config functions. The root cause is improper input validation of the X-Forwarded-For HTTP header (CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component). The X-Forwarded-For header is commonly used in reverse proxy scenarios to communicate the original client IP address; however, this header is user-controlled and can contain arbitrary values. When the get_client_ip function processes this header without proper sanitization before passing it downstream to the install_mcp_config function, an attacker can inject code (likely Python code given the backend context) that will be interpreted rather than treated as literal data. The affected CPE is cpe:2.3:a:langflow-ai:langflow:*:*:*:*:*:*:*:* with versions up to 1.8.3 confirmed vulnerable.
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 NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
5DescriptionCVE.org
A vulnerability was detected in langflow-ai langflow up to 1.8.3. The impacted element is the function get_client_ip/install_mcp_config of the file src/backend/base/langflow/api/v1/mcp_projects.py of the component Model Context Protocol Configuration API. Performing a manipulation of the argument X-Forwarded-For results in injection. The attack may be initiated remotely. The exploit is now public and may be used. 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.
Related Vulnerabilities in langflow-ai langflow Multiple Vulnerabilities
View all 5Langflow 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-23762
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB