# CVE-2026-0770: Langflow Inclusion of Functionality from Untrusted Control Sphere

> Remote attackers can execute arbitrary code as root via the validate endpoint without authentication, requiring immediate patching.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 21 Jul 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-g22f-v6f7-2hrh, PYSEC-2026-1525

## What is CVE-2026-0770?

CVE-2026-0770 is a critical code injection vulnerability in Langflow Langflow, published on 23 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

## Which versions are affected by CVE-2026-0770?

3 open source packages ship an affected version, including langflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `langflow` | PyPI | All versions to 1.7.3 | None |
| `langflow` | PyPI | All versions to 1.7.3 | None |
| `langflow` | PyPI | All versions to 1.7.3 | None |

Products: Langflow Langflow.

## How do I fix CVE-2026-0770?

No fix has been published for CVE-2026-0770 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 24 Jul 2026.

## Is CVE-2026-0770 being exploited?

Yes. Attackers have exploited CVE-2026-0770 in the wild since at least 21 Jul 2026.

Public exploit code:

- Proof of Concept for CVE-2026-0770 - Langflow Remote Code Execution (github_poc): https://github.com/affix/CVE-2026-0770-PoC
- Langflow Remote Code Execution (RCE) Proof-of-Concept (github_poc): https://github.com/0xgh057r3c0n/CVE-2026-0770
- CVE-2026-0770 (github_poc): https://github.com/0xredash/CVE-2026-0770
- https://github.com/Yetazyyy/CVE-2026-0770 (github_poc): https://github.com/Yetazyyy/CVE-2026-0770
- LangFlow RCE | CVE-2026-0770 | Proof-Of-Concept (github_poc): https://github.com/Ez4rd1x1/CVE-2026-0770
- Langflow Unauthenticated RCE (validate endpoint) (metasploit)

## Other vulnerabilities in Langflow Langflow

- [CVE-2026-9198](https://insights.sbomify.com/CVE-2026-9198/): IBM Langflow Code Injection (critical 9.8, exploited in the wild)
- [CVE-2025-3248](https://insights.sbomify.com/CVE-2025-3248/): Langflow Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2025-34291](https://insights.sbomify.com/CVE-2025-34291/): Langflow Origin Validation Error (critical 9.4, exploited in the wild)
- [CVE-2026-33017](https://insights.sbomify.com/CVE-2026-33017/): Langflow Code Injection (critical 9.3, exploited in the wild)
- [CVE-2026-55255](https://insights.sbomify.com/CVE-2026-55255/): Langflow Authorization Bypass Through User-Controlled Key (high 8.4, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0770 and fix it if it is affected.

What it is: CVE-2026-0770 is a critical code injection vulnerability in Langflow Langflow, published on 23 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-0770 in the wild since at least 21 Jul 2026.

Affected packages and fixed versions:
- langflow (PyPI): affected all versions up to 1.7.3; no fix listed
- langflow (PyPI): affected all versions up to 1.7.3; no fix listed
- langflow (PyPI): affected all versions up to 1.7.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0770/ (Markdown: https://insights.sbomify.com/CVE-2026-0770/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0770
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0770
- OSV: https://osv.dev/vulnerability/CVE-2026-0770

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0770/
Summaries are generated and may contain mistakes; the official description above is the record.