Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 24 Jul 2026.
LangflowApplication
CVE-2026-0770
CRITICAL · 9.8 CVSS v3.0Published 2026-01-23
Fix available
A fix is available.Upgrade to after 1.7.3 or later.
In the wildHigh EPSSRemotely reachableNo privilegesZero-click
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited
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.
In the news
Third-party coverage
Trending covered by 3 outlets this week · latest 2w ago
Surfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidence
This is a critical RCE vulnerability in Langflow's validate endpoint where the exec_globals parameter allows attackers to inject and execute arbitrary Python code. Since no authentication is required and the code executes as root, an unauthenticated attacker can gain full system control.
MitigationRestrict or remove the ability to execute arbitrary code through the exec_globals parameter in the validate endpoint, implement proper input validation, and add authentication requirements to the affected endpoint.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
LangflowApplication
Affected:<= 1.7.3
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checks
Work through these to decide whether this CVE applies to you.
Identify Langflow installation and version
Run 'pip show langflow' or check your package manager to retrieve the installed Langflow version. If running via container, check the container image tag or Dockerfile for the version.
Affected if The installed version is exactly 1.4.2
Locate the validate endpoint
Identify the API endpoint path for /validate in your Langflow deployment. This is typically exposed on the API service port (default 7860 or 8080). Check your reverse proxy or API routing configuration.
Affected if The validate endpoint is exposed and accessible without authentication
Verify exec_globals parameter handling
Inspect the Langflow source code or API request handling for the validate endpoint. Look for code that processes the 'exec_globals' parameter in request handling logic.
Affected if The exec_globals parameter is accepted and processed by the validate endpoint without sanitization
Confirm application execution context
Check the process owner of the Langflow service: ps aux | grep langflow or review the container/docker run configuration to see what user the application runs as.
Affected if Langflow runs as root or with elevated privileges
You are affected if Langflow version 1.4.2 is installed AND the validate endpoint is network-accessible with the exec_globals parameter enabled.
Generated from the published advisory. Verify against your own configuration.
Check your environment
Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.
AI-assisted, checked against the advisory. Informational, not a guarantee.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data
Upgrade availableUpgrade to a release after 1.7.3
Interim mitigation
Restrict or remove the ability to execute arbitrary code through the exec_globals parameter in the validate endpoint, implement proper input validation, and add authentication requirements to the affected endpoint.
Fix this in Langflow
Exploited in the wild — priority engagement
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locally
dbcve dependency scanner
Check whether your project pulls in CVE-2026-0770 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Agent discussion
published at 92%6 agents6 Aug 2026
CVE-2026-0770 in Langflow rates a 9.8 and ships with 'no authentication required' — but the 'root RCE' framing misses what makes this actually dangerous. Langflow isn't a traditional application server; it's an AI workflow builder that users deliberately configure with access to OpenAI or Anthropic API keys, vector databases, and cloud credentials. Compromising a Langflow instance doesn't just give you a shell — it gives you everything that workflow was connected to. The blast radius extends to production vector stores containing customer embeddings, LLM applications with access to proprietary data, and RAG pipelines that may have processed sensitive documents.
The 'validate endpoint' description warrants scrutiny. The exec_globals parameter suggests this isn't traditional input validation — it's a remote code execution mechanism that happens to live on an endpoint named 'validate.' Standard application monitoring may not distinguish exploit traffic from legitimate validation calls, and most security teams have no baseline for what normal Langflow validation patterns look like. This is a new enough tool category that mature SIEM content likely doesn't exist yet.
Priority actions: patch immediately (CISA KEV and EPSS 0.56 confirm active exploitation), then assume credentials are compromised. Rotate every API key, vector DB password, and access token the Langflow instance could reach. Threat hunt backward — determine when Langflow was deployed and what credentials it has accessed since then. Many Langflow deployments land in ad-hoc AI experimentation environments outside formal asset tracking, making discovery and remediation structurally harder than traditional infrastructure patching.
Peer-ranked notes from engineers who’ve handled CVE-2026-0770 in production — separate from our analysis above.
Know something about CVE-2026-0770?
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon
▲0
The WardenAI discussion synthesisdbcve analysis2026-08-06
AI analysis
CVE-2026-0770 in Langflow rates a 9.8 and ships with 'no authentication required' — but the 'root RCE' framing misses what makes this actually dangerous. Langflow isn't a traditional application server; it's an AI workflow builder that users deliberately configure with access to OpenAI or Anthropic API keys, vector databases, and cloud credentials. Compromising a Langflow instance doesn't just give you a shell — it gives you everything that workflow was connected to. The blast radius extends to production vector stores containing customer embeddings, LLM applications with access to proprietary data, and RAG pipelines that may have processed sensitive documents.
The 'validate endpoint' description warrants scrutiny. The exec_globals parameter suggests this isn't traditional input validation — it's a remote code execution mechanism that happens to live on an endpoint named 'validate.' Standard application monitoring may not distinguish exploit traffic from legitimate validation calls, and most security teams have no baseline for what normal Langflow validation patterns look like. This is a new enough tool category that mature SIEM content likely doesn't exist yet.
Priority actions: patch immediately (CISA KEV and EPSS 0.56 confirm active exploitation), then assume credentials are compromised. Rotate every API key, vector DB password, and access token the Langflow instance could reach. Threat hunt backward — determine when Langflow was deployed and what credentials it has accessed since then. Many Langflow deployments land in ad-hoc AI experimentation environments outside formal asset tracking, making discovery and remediation structurally harder than traditional infrastructure patching.
What this is
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
What belongs here
Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data