Langflow Langflow
Langflow Langflow is affected by a critical-severity vulnerability (CVE-2026-0770) that is confirmed to be actively exploited in the wild. 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.
What is this 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.
How it works
This is classified as CWE-829. In plain terms, an attacker could use this flaw in Langflow to gain access, disrupt service, or steal data — the exact impact depends on how it’s deployed in your environment.
CVSS vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
Mitigations
- Apply the vendor’s security patch or update as soon as it’s available and tested.
- If no patch exists yet, apply the vendor’s temporary workaround.
- Limit network exposure of the affected system until it’s patched.
- Review logs for signs of prior exploitation, especially if it’s flagged for ransomware use.
Recommendations
- Confirm whether Langflow Langflow is used anywhere in your environment.
- Patch internet-facing systems first, then internal ones.
- Set a reminder ahead of the remediation deadline so it doesn’t slip.
- Subscribe to the vendor’s security advisories for earlier warning next time.
Compiled from public threat intelligence (CISA Known Exploited Vulnerabilities catalog and the National Vulnerability Database, referenced in 1 public advisories).