# CVE-2025-57760: Langflow Vulnerable to Privilege Escalation via CLI Superuser Creation

> Authenticated users with RCE access can escalate privileges to superuser by invoking an internal CLI command in Langflow.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Aug 2025
- **Updated:** 25 Aug 2025
- **Also known as:** GHSA-4gv9-mp8m-592r, PYSEC-2025-243, PYSEC-2026-1526

## What is CVE-2025-57760?

CVE-2025-57760 is a high-severity vulnerability in Langflow Langflow, published on 25 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Langflow is a tool for building and deploying AI-powered agents and workflows. A privilege escalation vulnerability exists in Langflow containers where an authenticated user with RCE access can invoke the internal CLI command langflow superuser to create a new administrative user. This results in full superuser access, even if the user initially registered through the UI as a regular (non-admin) account. A patched version has not been made public at this time.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-57760?

6 open source packages ship an affected version, including langflow and langflow-base. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `langflow` | PyPI | All versions | 1.5.0 |
| `langflow` | PyPI | All versions | 1.5.1 |
| `langflow` | PyPI | All versions | 1.5.1 |
| `langflow-base` | PyPI | All versions | 0.5.1 |
| `langflow-base` | PyPI | All versions | 0.5.1 |
| `langflow-base` | PyPI | All versions | 0.5.1 |

Products: Langflow Langflow.

## How do I fix CVE-2025-57760?

Upgrade langflow to a fixed version for your release line: 1.5.0 or 1.5.1.

## Is CVE-2025-57760 being exploited?

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

## 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-2025-57760 and fix it if it is affected.

What it is: CVE-2025-57760 is a high-severity vulnerability in Langflow Langflow, published on 25 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57760 exists.

Affected packages and fixed versions:
- langflow (PyPI): affected all versions; fixed in 1.5.0
- langflow (PyPI): affected all versions; fixed in 1.5.1
- langflow (PyPI): affected all versions; fixed in 1.5.1
- langflow-base (PyPI): affected all versions; fixed in 0.5.1
- langflow-base (PyPI): affected all versions; fixed in 0.5.1
- langflow-base (PyPI): affected all versions; fixed in 0.5.1

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

## Sources

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

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