Langflow code Code Injection Remote Code Execution Vulnerability

published 2026-01-23 9 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-4453

cvss: 9.8; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 28.1%; EPSS 28.1% chance of exploitation in 30 days, percentile 98%
public exploits: 1; Metasploit, plus a Nuclei check

Langflow code Code Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Langflow. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the handling of the code parameter provided to the validate endpoint. The issue results from the lack of proper validation of a user-supplied string before using it to execute Python code. An attacker can leverage this vulnerability to execute code in the context of root. . Was ZDI-CAN-27322.

Timeline

2026-01-23 Published
2026-09-02 First public exploit (Metasploit exploit/multi/http/langflow_unauth_rce_cve_2026_0768)

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: total
Assessed: 9 mo ago (2026-01-24)

Exploit prediction

28.05% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

Metasploit exploit/multi/http/langflow_unauth_rce_cve_2026_0768 Langflow AI Validate Code Injection unauth RCE metasploit exploit, excellent rank, 2026-09-02
Nuclei template Langflow <=1.2.x - Unauthenticated Remote Code Execution via validate_code nuclei detection template

CVSS scores

assigned by	version	score	vector
CNA	3.0	9.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Langflow Langflow

Classification

Weakness

CWE-94 Improper Control of Generation of Code

References

zerodayinitiative.com /advisories/ZDI-26-034/
third-party-advisory

Sources

CVE List CVE-2026-0768
NVD CVE-2026-0768

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary