Is CVE-2026-0770 exploited in the wild?

Yes. CVE-2026-0770 is known to be exploited in the wild, first recorded on 21 July 2026. Treat it as urgent.

How severe is CVE-2026-0770?

Critical severity, with a CVSS score of 9.8, published 23 January 2026.

Which products and versions are affected?

Langflow 1.4.2; langflow (PyPI) ECOSYSTEM:introduced=0,last_affected=1.7.3.

Is there a fix for CVE-2026-0770?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-0770 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-0770?

Check whether you run Langflow or langflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-0770: Langflow remote code execution in validate endpoint

CVE-2026-0770 · Severity: critical · CVSS 9.8 · Exploited in the wild · Published 2026-01-23

Langflow, a visual framework for building multi-agent and RAG applications, contains a critical vulnerability that allows an unauthenticated attacker to take full control of the server. By sending a specially crafted request to a specific system endpoint, an attacker can execute arbitrary commands with administrative (root) privileges. This could lead to the complete theft of sensitive AI models, data, and credentials, or the total disruption of the service.

Technologies: Langflow, langflow (PyPI). Vendors: Langflow, PyPI.

Quick answers

Is CVE-2026-0770 exploited in the wild?: Yes. CVE-2026-0770 is known to be exploited in the wild, first recorded on 21 July 2026. Treat it as urgent.
How severe is CVE-2026-0770?: Critical severity, with a CVSS score of 9.8, published 23 January 2026.
Which products and versions are affected?: Langflow 1.4.2; langflow (PyPI) ECOSYSTEM:introduced=0,last_affected=1.7.3.
Is there a fix for CVE-2026-0770?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-0770 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-0770?: Check whether you run Langflow or langflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A remote code execution vulnerability exists in Langflow due to the inclusion of functionality from an untrusted control sphere (CWE-829). The flaw is located within the handling of the 'exec_globals' parameter provided to the '/validate' endpoint. An unauthenticated remote attacker can exploit this by submitting a malicious payload that is subsequently executed by the server. Successful exploitation allows for arbitrary code execution in the context of the root user. While version 1.4.2 is explicitly identified as affected, users are advised to update to version 1.9.0 or later to remediate the issue.

Affected products

Langflow Langflow 1.4.2

Identifiers

CVE-2026-0770
GHSA-g22f-v6f7-2hrh
PYSEC-2026-1525

Timeline

2025-07-18: disclosed: Vulnerability reported to vendor by ZDI
2026-01-09: advisory: Coordinated public release of ZDI advisory
2026-01-23: advisory: NVD publication date
2026-07-21: kev added: Added to CISA KEV catalog

References

https://www.zerodayinitiative.com/advisories/ZDI-26-036/

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.