Security readout for executives and security teams
Plain-English summary
CVE-2026-0771 is a high-severity remote code execution issue in Langflow 1.4.2. If an attacker can introduce custom Python code into a workflow through Python function components, code may run in the context of the Langflow application. Exploitability depends on how Langflow is configured and exposed.
Executive priority
Treat as a high-priority exposure review for any Langflow 1.4.2 deployment, especially shared or externally reachable instances. Prioritize access restriction and vendor patch confirmation because the issue can lead to application-context code execution.
Technical view
The flaw is a CWE-94 code injection vulnerability in Langflow's handling of Python function components. The provided CVSS v3.0 score is 7.1 with AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H, indicating network reachability but requiring low privileges, user interaction, and high attack complexity. The source bundle identifies Langflow 1.4.2 as affected and does not provide evidence of a fixed version.
Likely exposure
Organizations running Langflow 1.4.2 are the stated affected population. Risk is higher where Langflow is reachable by untrusted users, supports multi-user workflow authoring, or permits custom Python function components in workflows. Exact exposure depends on product configuration.
Exploitation context
No active exploitation is stated in the source bundle, and KEV is false. The advisory describes potential arbitrary code execution through custom Python introduced into a workflow, but exploitation details vary by configuration and are not expanded here.
Researcher notes
Source data identifies ZDI-CAN-27497 / ZDI-26-037, CWE-94, Langflow 1.4.2, CVE publication on 2026-01-23, and update on 2026-02-26. The bundle does not include public exploit evidence, KEV listing, or a confirmed fixed release.
Mitigation direction
- Identify whether Langflow 1.4.2 is deployed and where it is exposed.
- Restrict Langflow access to trusted users and trusted networks, especially workflow creation or editing surfaces.
- Limit or disable custom Python function component usage where operationally possible until vendor guidance is reviewed.
- Run Langflow with least-privilege service accounts and isolation appropriate for code-execution risk.
- Review Langflow, CVE, and ZDI/vendor guidance for an official patched version or mitigation; patch evidence is not included in the provided bundle.
- If compromise is suspected, preserve logs, review recent workflow changes, rotate exposed secrets, and rebuild affected runtime environments as appropriate.
Validation and detection
- Confirm deployed Langflow versions and flag any instance running 1.4.2.
- Review who can create, import, or modify workflows containing Python function components.
- Check whether Langflow is internet-facing or reachable from lower-trust network segments.
- Review application and platform logs for unexpected workflow creation, modification, or execution activity.
- Verify whether official vendor guidance identifies a fixed version or configuration mitigation before closing the finding.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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.
Open ATT&CK lookupExecution behavior lookup
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.
Open ATT&CK lookupCVE-2026-0771 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H1.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
7.1HighVector: CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- ZDI-26-037CVE reference · x_research-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.