CVE-2026-0770ExploitPublished 29 May 2026

Langflow 1.3.0 · Remote Code Execution

Affects https://github.com/langflow-ai/langflowSource Exploit-DB RSS Feed

Authoritative record:CVE-2026-0770· Critical 9.8

Exploited in the wild · KEV due 24 Jul 2026 · public exploit available (Metasploit, Exploit-DB) · 62% EPSS : apply the vendor's fix or mitigations to https://github.com/langflow-ai/langflow now.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.0 base score

9.8Critical

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

KEV deadline: 24 Jul 2026 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
EPSS: 62.5% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/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

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 23 Jan 2026
Detectable: evidence found.
nuclei template: Langflow < 1.3.0 - Remote Code Execution via validate_code() exec()
Weaponized: evidence found.
1 Metasploit module · 1 Exploit-DB entry, 126 days after disclosure
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 179 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE published
on cve.org
23 Jan 202603:28 UTC, t = 0
First Exploit-DB entry (opens in a new tab)
Langflow 1.3.0 - Remote Code Execution
29 May 2026, 126 days after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
21 Jul 2026, 179 days after disclosure
KEV remediation due
US federal deadline
24 Jul 2026, 182 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Affected software

Product	Affected	Fixed in
LangflowLangflow	Affected =1.4.2	Fixed in–

Description

Langflow 1.3.0 - Remote Code Execution

Impact

Successful exploitation of this vulnerability could allow an attacker to execute arbitrary code remotely on systems running Langflow 1.2.0, potentially leading to full system compromise depending on the privileges of the application.

Mitigation

Until an official fix is released, consider restricting network access to the vulnerable service and monitoring for suspicious activity related to Langflow 1.2.0.

Public tooling indexed from Metasploit Framework, Exploit-DB, ProjectDiscovery nuclei-templates and PoC-in-GitHub. Its existence raises the odds of exploitation; it does not confirm attacks.

CWE-829Inclusion of Functionality from Untrusted Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Vulnerable Dependency Management (opens in a new tab)
Software Supply Chain Security (opens in a new tab)
Infrastructure as Code (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.6 (opens in a new tab)
V14.2.3 (opens in a new tab)
V14.2.4 (opens in a new tab)
Attack patterns
Serialized Data External Linking (opens in a new tab)
DTD Injection (opens in a new tab)
Local Code Inclusion (opens in a new tab)
PHP Local File Inclusion (opens in a new tab)
Remote Code Inclusion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

Indicators of compromise

Exploit source code

Exploit code for Langflow 1.3.0 - Remote Code Execution3,556 characters

# Exploit Title: Langflow  1.3.0 - Remote Code Execution 
# Fofa-dork: title="Langflow"
# Shodan-dork: title:"Langflow"
# Date: 23-05-2026
# Exploit Author: Diamorphine
# Venodor Homepage: https://www.langflow.org/
# Software Link: https://github.com/langflow-ai/langflow
# Version: 1.2.0
# Tested on: Debian
# CVE : CVE-2026-0770
# Description:  Langflow contains a remote code execution caused by inclusion of functionality from untrusted control sphere in the exec_globals parameter at the validat…

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Aug 2026, 05:03 UTC

Public exploits and detection1 Metasploit module, 1 Exploit-DB entry, a Nuclei detection template, GitHub proofs of concept

WeaknessesCWE-829

Technical details

Indicators of compromise

Exploit source code

References

Community reviews

Related threats