CVE-2024-42835: Langflow: Unauthenticated RCE via PythonCodeTool
GHSA-56m6-4mhw-h3g5 CRITICAL PoC AVAILABLE CISA: ATTENDAny Langflow instance ≤1.0.12 exposed to the network is a critical liability — unauthenticated attackers can execute arbitrary code with the privileges of the Langflow process. Take all public-facing Langflow deployments offline immediately or restrict access to VPN/allowlisted IPs. Given no official patch is listed, assume compromise on any externally-facing instance and investigate for lateral movement to cloud credentials and LLM API keys.
Risk Assessment
Severity is as high as it gets: CVSS 9.8 with network-accessible, zero-authentication, zero-interaction exploitation. EPSS of ~16% indicates active exploitation interest from the security community. Langflow is commonly deployed in cloud environments (often with public-facing dashboards for team collaboration), dramatically widening the attack surface. The combination of no auth + code execution in an AI framework creates a direct path to cloud credentials, LLM API keys, and connected data stores.
Affected Systems
Severity & Risk
Attack Surface
Recommended Action
5 steps-
IMMEDIATE
Isolate all Langflow instances ≤1.0.12 behind VPN or firewall rules; remove any public internet exposure.
-
AUDIT
Review Langflow deployment configs for hardcoded API keys, credentials, or service account tokens — rotate all of them.
-
PATCH
Monitor the Langflow GitHub repo and pip releases for a patched version; no official fix was available at CVE publication.
-
DETECT
Review logs for unusual Python process spawning, outbound connections from the Langflow process, and unexpected file writes.
-
CONTAIN
If compromise is suspected, treat the host as compromised — rotate all credentials accessible from that environment and review downstream connected services.
CISA SSVC Assessment
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
Classification
Compliance Impact
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2024-42835?
Any Langflow instance ≤1.0.12 exposed to the network is a critical liability — unauthenticated attackers can execute arbitrary code with the privileges of the Langflow process. Take all public-facing Langflow deployments offline immediately or restrict access to VPN/allowlisted IPs. Given no official patch is listed, assume compromise on any externally-facing instance and investigate for lateral movement to cloud credentials and LLM API keys.
Is CVE-2024-42835 actively exploited?
Proof-of-concept exploit code is publicly available for CVE-2024-42835, increasing the risk of exploitation.
How to fix CVE-2024-42835?
1. IMMEDIATE: Isolate all Langflow instances ≤1.0.12 behind VPN or firewall rules; remove any public internet exposure. 2. AUDIT: Review Langflow deployment configs for hardcoded API keys, credentials, or service account tokens — rotate all of them. 3. PATCH: Monitor the Langflow GitHub repo and pip releases for a patched version; no official fix was available at CVE publication. 4. DETECT: Review logs for unusual Python process spawning, outbound connections from the Langflow process, and unexpected file writes. 5. CONTAIN: If compromise is suspected, treat the host as compromised — rotate all credentials accessible from that environment and review downstream connected services.
What systems are affected by CVE-2024-42835?
This vulnerability affects the following AI/ML architecture patterns: LLM workflow builders, Visual AI pipeline editors, AI agent frameworks, RAG pipeline development environments, LLM application prototyping platforms.
What is the CVSS score for CVE-2024-42835?
CVE-2024-42835 has a CVSS v3.1 base score of 9.8 (CRITICAL). The EPSS exploitation probability is 14.31%.
Technical Details
NVD Description
langflow v1.0.12 was discovered to contain a remote code execution (RCE) vulnerability via the PythonCodeTool component.
Exploitation Scenario
An attacker scans for exposed Langflow instances (Shodan/Censys queries for Langflow UI signatures are trivial). They access the unauthenticated web UI or API endpoint, create a flow using the PythonCodeTool component, and inject a Python reverse shell payload. Upon execution, they gain shell access as the Langflow process user. From there, they extract environment variables and config files to harvest LLM API keys, database credentials, and cloud provider tokens. With API key access, they can exfiltrate proprietary prompts, fine-tuning data, or conduct cost-harvesting attacks at the victim's expense.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References
Timeline
Related Vulnerabilities
CVE-2026-33309 9.9 langflow: Path Traversal enables file access
Same package: langflow CVE-2024-37014 9.8 Langflow: unauthenticated RCE via custom component API
Same package: langflow CVE-2026-27966 9.8 langflow: Code Injection enables RCE
Same package: langflow CVE-2026-33017 9.8 langflow: Code Injection enables RCE
Same package: langflow CVE-2024-48061 9.8 Langflow: RCE via unsandboxed code component execution
Same package: langflow
AI Threat Alert