# CVE-2026-0768: Langflow code Code Injection Remote Code Execution Vulnerability

> Remote attackers can execute arbitrary code as root via the validate endpoint due to improper validation of user-supplied Python code.

- **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:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-x5pr-rvjj-j6qm

## What is CVE-2026-0768?

CVE-2026-0768 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 code Code Injection 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 code parameter provided to the validate endpoint. The issue results from the lack of proper validation of a user-supplied string before using it to execute Python code. An attacker can leverage this vulnerability to execute code in the context of root.
. Was ZDI-CAN-27322.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Langflow Langflow.

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

No fix has been published for CVE-2026-0768 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-0768 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0768 exists.

Public exploit code:

- CVE-2026-0768 - Draft or TODO (github_poc): https://github.com/HORKimhab/CVE-2026-0768
- Langflow AI Validate Code Injection unauth RCE (metasploit)
- Proof of concept exploit code for CVE-2026-0768 (github_poc): https://github.com/rmhowe425/POC-CVE-2026-0768
- Langflow <=1.2.x - Unauthenticated Remote Code Execution via validate_code (nuclei): http/cves/2026/CVE-2026-0768.yaml

## 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-2026-0770](https://insights.sbomify.com/CVE-2026-0770/): Langflow Inclusion of Functionality from Untrusted Control Sphere (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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0768 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0768 exists.

Affected product: Langflow Langflow. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-0768/ (Markdown: https://insights.sbomify.com/CVE-2026-0768/index.md)
```

## Sources

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

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