VulnerabilityPublished 31 Oct 2024Updated 27 Mar 2026

CVE-2024-42835: langflow

Affects langflowSource CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

9.8Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.1% chance of exploitation in 30 days – higher than 67% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PyPIlangflow`pkg:pypi/langflow`Other threats	Affected =1.0.12	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-42835, organizations should immediately restrict network access to langflow instances, ensuring they are not exposed to untrusted networks or the internet. Implement network segmentation and firewall rules to limit communication to trusted users and systems only. Disable or isolate the PythonCodeTool component if feasible until a patch is available, or run it within a tightly controlled sandbox environment that restricts code execution capabilities. Monitor logs and network traffic for unusual activity indicative of exploitation attempts, such as unexpected Python code execution or anomalous outbound connections. Employ application-layer firewalls or runtime application self-protection (RASP) solutions to detect and block malicious payloads targeting langflow. Stay informed about vendor updates and apply patches promptly once released. Additionally, conduct security reviews of AI workflow tools and enforce strict input validation and code execution policies. Educate developers and administrators about the risks of remote code execution vulnerabilities and the importance of secure configuration and access controls.

Description

langflow v1.0.12 was discovered to contain a remote code execution (RCE) vulnerability via the PythonCodeTool component.

Impact

The impact of CVE-2024-42835 is severe and wide-ranging. Successful exploitation can result in complete system compromise, allowing attackers to execute arbitrary commands, access sensitive data, modify or delete critical files, and disrupt service availability. This undermines the confidentiality, integrity, and availability of affected systems. Organizations relying on langflow for AI workflow orchestration risk exposure of intellectual property, customer data, and internal processes. The vulnerability could be leveraged as an entry point for broader network intrusions, ransomware deployment, or espionage activities. Given the lack of authentication and user interaction requirements, attackers can automate exploitation at scale, increasing the threat surface. The absence of known exploits in the wild currently provides a limited window for remediation before active exploitation emerges. Industries with high AI adoption or those integrating langflow into critical infrastructure are particularly vulnerable, potentially leading to operational downtime, financial losses, reputational damage, and regulatory penalties.

References

github.com/langflow-ai/langflow/issues/2908 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 18:13 UTC

Technical details

References

Community reviews

Related threats