CriticalCVE-2026-0770

    Langflow Inclusion of Functionality from Untrusted Control Sphere Vulnerability (CVE-2026-0770)

    Published Last modified In CISA KEV since Sources: CVE.org, SingCERT, pwn.watch, OSV

    Share

    What is affected, what to do

    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.

    The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Langflow eq 1.4.2..1.4.2

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org, SingCERT, pwn.watch, OSV

    62.6 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.19

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    241.30 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab), CSA/SingCERT How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    62.6 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.19
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 23 January 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-829

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw is network-reachable with no authentication and no user interaction, and it yields code execution as root. A single request is enough for full compromise of confidentiality, integrity and availability. Its exploitation likelihood ranks among the very highest of all tracked CVEs. Exposed Langflow servers are mass-scanned, typically for cryptomining, botnet enrolment and harvesting high-value LLM and cloud API keys. CISA records no known ransomware use. Treat any internet-facing instance as critical with immediate action, and internal instances holding production credentials as high. Isolated dev instances with no external reachability can follow the regular patch cycle.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Kill internet exposure now: Inventory every Langflow instance (default port 7860/TCP plus any reverse-proxy front ends) and cut all internet-reachable access via perimeter firewall, security group or ingress removal. No authentication is needed to exploit this flaw, so treat any instance that was reachable as potentially compromised.
      • Identify affected versions: The context lists Langflow 1.4.2 and 1.7.3 as affected, along with PyPI langflow 0.0.32, 0.0.33, 0.0.40, 0.0.44, 0.0.45 and 0.0.46. Confirm the installed version via pip show langflow or the container image tag. A patch is available from the vendor — look up the fixed version in the vendor advisory or the ZDI advisory (ZDI-CAN-27325) and verify it before rollout.
      • Block the validate endpoint: Until you upgrade, have the reverse proxy or WAF return 403 for /api/v1/validate/ (especially /api/v1/validate/code). Normal flow execution does not depend on it.
      • Preserve evidence, then rebuild: For previously exposed hosts, capture a container or host snapshot, access logs and the running process list. Then rebuild from a trusted image rather than attempting cleanup, because attacker code ran as root.
      • Rotate secrets: Rotate every LLM provider API key stored in Langflow (OpenAI, Azure, Anthropic, etc.), plus vector DB, database and cloud credentials, LANGFLOW_SECRET_KEY and all process environment variables. If flows handled personal data, assess GDPR and NIS2 notification duties.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Run Langflow only on an internal dev or management VLAN. Allow access solely through VPN or a zero-trust proxy that enforces authentication upfront (e.g. OIDC via oauth2-proxy), and never publish 7860 directly.
      • WAF/IPS rule: Drop request bodies to /api/v1/validate/* that contain exec_globals, __import__, os.system, subprocess, eval( or exec(. A Suricata starting point is http.uri; content:"/api/v1/validate"; http.request_body; content:"exec_globals"; nocase; with alert or drop.
      • Container hardening: Run the container as non-root (USER or runAsNonRoot: true) with cap_drop: ALL and readOnlyRootFilesystem, keeping the default seccomp/AppArmor profiles. Do not mount the Docker socket or host paths.
      • Egress filtering: Restrict outbound traffic from Langflow hosts to an allowlist of the required LLM and API endpoints. This breaks reverse shells, stage-two downloads and exfiltration.
      • Configuration and IAM: Set LANGFLOW_AUTO_LOGIN=false and use strong superuser credentials. Scope the host's cloud role or service account to least privilege, and block the instance metadata service (169.254.169.254) or enforce IMDSv2.

    3. Runbook step 3

      Detection rules

      • Web/proxy access logs: Look for POSTs to /api/v1/validate/code or /api/v1/validate/* from external or unknown source IPs, especially without a preceding login session. SPL: index=proxy uri_path="/api/v1/validate/*" http_method=POST | stats count by src_ip, uri_path, status.
      • EDR process ancestry: Alert when the Langflow Python or uvicorn process spawns sh, bash, curl, wget, nc, python -c or base64. KQL: DeviceProcessEvents | where InitiatingProcessCommandLine has "langflow" and FileName in~ ("sh","bash","curl","wget","nc").
      • Linux auditd / Sysmon for Linux (EID 1): Watch for execve events with uid=0 whose parent is the Langflow worker, e.g. -a always,exit -F arch=b64 -S execve -F ppid=<langflow_pid> -k langflow_exec. A Sigma rule should match ParentImage|endswith: python* and ParentCommandLine|contains: langflow.
      • Network telemetry (Zeek/Suricata): Flag new outbound connections from Langflow hosts to unfamiliar IPs, odd ports, or paste and file-sharing services. Treat container requests to 169.254.169.254 as suspicious, and diff conn.log and http.log against the egress baseline.
      • Persistence artefacts: Hunt for new cron entries, modified ~/.ssh/authorized_keys, unknown binaries in /tmp or /dev/shm, and coin-miner processes with sustained high CPU on Langflow hosts.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: CISA KEV Catalog, NVD (NIST), CVE.org (MITRE), CSA/SingCERT, pwn.watch, OSV (Open Source Vulnerabilities), cvelistv5

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    LangflowLangflow
    • 1.4.2
    • —
    langflowlangflow
    • ≤ 1.7.3
    • —
    pypilangflow
    • 0.6.5a9
    • 0.5.0a3
    • 0.6.3a1
    • 0.6.1
    • 1.6.8
    • 1.0.0a6
    • 0.6.5a0
    • 1.0.18
    • 0.6.3
    • 1.0.17
    • 0.5.12
    • 1.0.0a59
    • 0.5.0a1
    • 0.4.7
    • 0.3.3
    • 0.0.31
    • 1.0.19.post2
    • 0.2.8
    • 1.0.0a32
    • 1.0.0a45
    • 1.0.0a23
    • 1.0.0a28
    • 0.0.73
    • 1.0.6
    • 0.1.0
    • 0.6.3a4
    • 0.5.9
    • 0.6.8
    • 0.2.6
    • 0.5.0a5
    • 0.0.78
    • 1.7.1
    • 1.3.0
    • 1.1.3
    • 1.0.0a1
    • 1.7.0
    • 0.4.16
    • 0.5.10
    • 0.2.3
    • 0.2.12
    • 1.0.0a39
    • 0.5.0b3
    • 1.0.0a50
    • 0.3.4
    • 0.6.5a10
    • 0.5.6
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-829Inclusion of Functionality from Untrusted Control Sphere

      Base

      The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.

      Entry at MITRE CWE-829

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    CSA/SingCERTCritical Vulnerability in Langflow (opens in a new tab)CSA/SingCERTactively exploited
    GitHubaffix/CVE-2026-0770-PoC (opens in a new tab)github.comPoC (publicly reported)reported, not verified—
    PoC-in-GitHub (nomi-sec)cve-2026-0770-langflow_rce_reproduction (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-0770 (opens in a new tab)github.comPoC (publicly reported)reported, not verified

    References & sources

    • NVD (NIST)NVD: CVE-2026-0770advisory, pwn-watch
    • github.comaffix/CVE-2026-0770-PoCweb
    • github.comlangflow-ai/langflowpackage
    • zerodayinitiative.comadvisories/ZDI-26-036web
    • zerodayinitiative.comZDI-26-036x_research-advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-0770government-resource
    • pwn.watchpwn.watch: Langflow Langflow: Langflow Inclusion of Functionality from Untrusted Control Sphere Vulnerabilitypwn-watch
    • github.comLangflow Langflow — CVE-2026-0770pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: yes

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentchanged
      {"id":"CVE-2026-0770","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-07-21T15:45:21.869284Z"}
      {"id":"CVE-2026-0770","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-01-23T00:00:00+00:00"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. NVD analysis modifiedNVD

      Product mapping changed:
      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Product configurationchanged
      OR *cpe:2.3:a:langflow:langflow:1.4.2:-:*:*:*:*:*:*
      OR *cpe:2.3:a:langflow:langflow:*:*:*:*:*:*:*:* versions up to (including) 1.7.3
      Reference typeadded
      —
      CISA-ADP: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-0770 Types: US Government Resource

      Source identifier: nvd@nist.gov

    3. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: yes

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-0770
      SSVC assessmentchanged
      {"id":"CVE-2026-0770","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-02-24T04:56:28.363525Z"}
      {"id":"CVE-2026-0770","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-07-21T15:45:21.869284Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    4. CISA KEV entry updated9119a7d8…

      4 individual changes: Date Added, Due Date, Required Action, Vulnerability Name

      Show 4 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Date Addedadded
      —
      2026-07-21
      Due Dateadded
      —
      2026-07-21
      Required Actionadded
      —
      2026-07-21
      Vulnerability Nameadded
      —
      2026-07-21

      Source identifier: 9119a7d8-5eab-497f-8521-727c672e3725

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-0770
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-0770"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-0770.svg?lang=en" alt="CVE-2026-0770 – NEOSEC Intel" height="20"></a>