Summary
Langflow Vulnerable to Privilege Escalation via CLI Superuser Creation (Post-RCE)
Impact
- Privilege escalation to superuser, complete takeover of the Langflow instance
- Access to all user data, flows, stored credentials, and configuration
- Credential leakage, attacker can extract third-party API keys
- Exposure of environment variables (inside docker container)
- Ability to run additional Langflow instances via
langflow runinside the container, which may lead to resource exhaustion (CPU, memory) and service degradation. - Full user management, superuser can delete other users, reset their passwords
The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.
CVE-2025-57760 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.5.1, 0.5.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
langflow to 1.5.1 or later; langflow-base to 0.5.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-57760? CVE-2025-57760 is a high-severity improper privilege management vulnerability in langflow (pip), affecting versions <= 1.5.0. It is fixed in 1.5.1, 0.5.1. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
- How severe is CVE-2025-57760? CVE-2025-57760 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2025-57760?
langflow(pip) (versions <= 1.5.0)langflow-base(pip) (versions <= 0.5.0)
- Is there a fix for CVE-2025-57760? Yes. CVE-2025-57760 is fixed in 1.5.1, 0.5.1. Upgrade to this version or later.
- Is CVE-2025-57760 exploitable, and should I be worried? Whether CVE-2025-57760 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-57760 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-57760?
- Upgrade
langflowto 1.5.1 or later - Upgrade
langflow-baseto 0.5.1 or later
- Upgrade