CVE-2026-0770: Langflow exec_globals Inclusion of Functionality from Untrusted Control Sphere Remote Code Execution Vulnerability
Langflow exec_globals Inclusion of Functionality from Untrusted Control Sphere 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 exec_globals parameter provided to the validate endpoint. The issue results from the inclusion of a resource from an untrusted control sphere. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-27325.
Security readout for executives and security teams
Plain-English summary
Langflow 1.4.2 has a critical unauthenticated remote code execution flaw. The source states an attacker can abuse the validate endpoint’s exec_globals handling to run arbitrary code as root. Because CISA lists CVE-2026-0770 in KEV, treat internet-exposed Langflow as an urgent incident-risk item.
Executive priority
Prioritize within emergency patching and exposure reduction workflows. Known exploitation, unauthenticated network access, and root-level execution create credible risk of full system compromise.
Technical view
The vulnerability is CWE-829: inclusion of functionality from an untrusted control sphere. ZDI describes the flaw in the validate endpoint’s exec_globals parameter. Network attack complexity is low, no privileges or user interaction are required, and impact is high for confidentiality, integrity, and availability.
Likely exposure
Organizations running Langflow 1.4.2 are the only affected product/version identified in the supplied sources. Exposure is highest where Langflow is reachable from untrusted networks or runs with elevated privileges.
Exploitation context
CISA KEV status supports known exploitation. The provided sources do not include exploit timing, campaign details, indicators, or a fixed version. The reported execution context is root, increasing post-compromise impact.
Researcher notes
Evidence is strong for severity, affected version 1.4.2, unauthenticated RCE, vulnerable parameter, and KEV status. Evidence is incomplete for patched versions, exploit indicators, affected version range, and vendor-specific workarounds.
Mitigation direction
Inventory Langflow deployments and confirm whether version 1.4.2 is present.
Remove public access to Langflow until vendor remediation is confirmed.
Check Langflow and ZDI guidance for the corrected release or vendor mitigation.
Restrict access to trusted administrators using network controls and authentication layers.
Investigate exposed instances for compromise before returning them to service.
Validation and detection
Confirm Langflow version and deployment locations across hosts, containers, and cloud services.
Identify whether the validate endpoint is reachable from untrusted networks.
Review access logs for unexpected validate endpoint activity involving exec_globals.
Verify the service user and container privileges, especially root execution context.
Check CISA KEV entry and vendor advisories for remediation deadlines or updates.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-829: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Exploitation: activeAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-829 · source CWE mapping
Inclusion of Functionality from Untrusted Control Sphere
Inclusion of Functionality from Untrusted Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.