p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in langflow · Seite 2

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für langflow: 6. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 43

  1. CVE-2026-7700

    Mittel · CVSS 5.3EPSS 0,31%Öffentlicher ExploitKorrektur verfügbar

    langflow-ai langflow LambdaFilterComponent lambda_filter.py eval code injection

    A weakness has been identified in langflow-ai langflow up to 1.10.2. This affects the function eval of the file src/lfx/src/lfx/components/llm_operations/lambda_filter.py of the component LambdaFilterComponent. Executing a manipulation can lead to code injection. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

    • Auf 1.10.3 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-6599

    Mittel · CVSS 5.3EPSS 0,23%Keine Korrektur veröffentlicht

    langflow-ai langflow Model Context Protocol Configuration API mcp_projects.py install_mcp_config injection

    A vulnerability was detected in langflow-ai langflow up to 1.8.3. The impacted element is the function get_client_ip/install_mcp_config of the file src/backend/base/langflow/api/v1/mcp_projects.py of the component Model Context Protocol Configuration API. Performing a manipulation of the argument X-Forwarded-For results in injection. The attack may be initiated remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

    Veröffentlicht Aktualisiert
  3. CVE-2026-6598

    Mittel · CVSS 5.3EPSS 0,15%Korrektur verfügbar

    langflow-ai langflow Project Creation Endpoint projects.py encrypt_auth_settings cleartext storage in file

    A security vulnerability has been detected in langflow-ai langflow up to 1.8.3. The affected element is the function create_project/encrypt_auth_settings of the file src/backend/base/Langflow/api/v1/projects.py of the component Project Creation Endpoint. Such manipulation of the argument auth_settings leads to cleartext storage in a file or on disk. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

    • Auf 1.9.1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2026-6597

    Mittel · CVSS 5.1EPSS 0,32%Keine Korrektur veröffentlicht

    langflow-ai langflow Flow Using API core.py has_api_terms credentials storage

    A weakness has been identified in langflow-ai langflow up to 1.8.3. Impacted is the function remove_api_keys/has_api_terms of the file src/backend/base/langflow/api/utils/core.py of the component Flow Using API. This manipulation causes unprotected storage of credentials. The attack can be initiated remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

    Veröffentlicht Aktualisiert
  5. CVE-2026-34046

    Hoch · CVSS 8.7EPSS 0,48%Korrektur verfügbar

    Langflow: Authenticated Users Can Read, Modify, and Delete Any Flow via Missing Ownership Check

    Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to version 1.5.1, the `_read_flow` helper in `src/backend/base/langflow/api/v1/flows.py` branched on the `AUTO_LOGIN` setting to decide whether to filter by `user_id`. When `AUTO_LOGIN` was `False` (i.e., authentication was enabled), neither branch enforced an ownership check — the query returned any flow matching the given UUID regardless of who owned it. This allowed any authenticated user to read any other user's flow, including embedded plaintext API keys; modify the logic of another user's AI agents, and/or delete flows belonging to other users. The vuln

    • Auf 1.5.1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2026-33873

    Kritisch · CVSS 9.3EPSS 1,45%Korrektur verfügbar

    Langflow has Authenticated Code Execution in Agentic Assistant Validation

    Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to version 1.9.0, the Agentic Assistant feature in Langflow executes LLM-generated Python code during its validation phase. Although this phase appears intended to validate generated component code, the implementation reaches dynamic execution sinks and instantiates the generated class server-side. In deployments where an attacker can access the Agentic Assistant feature and influence the model output, this can result in arbitrary server-side Python execution. Version 1.9.0 fixes the issue.

    • Auf 1.9.0 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2026-33497

    Hoch · CVSS 8.7EPSS 19,58%Öffentlicher ExploitKorrektur verfügbar

    Langflow: /profile_pictures/{folder_name}/{file_name} endpoint file reading

    Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to version 1.7.1, in the download_profile_picture function of the /profile_pictures/{folder_name}/{file_name} endpoint, the folder_name and file_name parameters are not strictly filtered, which allows the secret_key to be read across directories. Version 1.7.1 contains a patch.

    • Auf 1.7.1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2026-33484

    Hoch · CVSS 7.5EPSS 5,94%Korrektur verfügbar

    Langflow has Unauthenticated IDOR on Image Downloads

    Langflow is a tool for building and deploying AI-powered agents and workflows. In versions 1.0.0 through 1.8.1, the `/api/v1/files/images/{flow_id}/{file_name}` endpoint serves image files without any authentication or ownership check. Any unauthenticated request with a known flow_id and file_name returns the image with HTTP 200. In a multi-tenant deployment, any attacker who can discover or guess a `flow_id` (UUIDs can be leaked through other API responses) can download any user's uploaded images without credentials. Version 1.9.0 contains a patch.

    • Auf 1.9.0 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2026-33309

    Kritisch · CVSS 10EPSS 13,47%Korrektur verfügbar

    Langflow has an Arbitrary File Write (RCE) via v2 API

    Langflow is a tool for building and deploying AI-powered agents and workflows. Versions 1.2.0 through 1.8.1 have a bypass of the patch for CVE-2025-68478 (External Control of File Name), leading to the root architectural issue within `LocalStorageService` remaining unresolved. Because the underlying storage layer lacks boundary containment checks, the system relies entirely on the HTTP-layer `ValidatedFileName` dependency. This defense-in-depth failure leaves the `POST /api/v2/files/` endpoint vulnerable to Arbitrary File Write. The multipart upload filename bypasses the path-parameter guard, allowing authenticated attackers to write files an

    • Auf 1.9.0 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2026-33053

    Mittel · CVSS 6.1EPSS 0,4%Korrektur verfügbar

    Langflow has Missing Ownership Verification in API Key Deletion (IDOR)

    Langflow is a tool for building and deploying AI-powered agents and workflows. In versions prior to 1.9.0, the delete_api_key_route() endpoint accepts an api_key_id path parameter and deletes it with only a generic authentication check (get_current_active_user dependency). However, the delete_api_key() CRUD function does NOT verify that the API key belongs to the current user before deletion.

    • Auf 1.9.0 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2026-33017

    Kritisch · CVSS 9.3EPSS 96,18%Im KEV-KatalogÖffentlicher ExploitKorrektur verfügbar

    Langflow has Unauthenticated Remote Code Execution via Public Flow Build Endpoint

    Langflow is a tool for building and deploying AI-powered agents and workflows. In versions prior to 1.9.0, the POST /api/v1/build_public_tmp/{flow_id}/flow endpoint allows building public flows without requiring authentication. When the optional data parameter is supplied, the endpoint uses attacker-controlled flow data (containing arbitrary Python code in node definitions) instead of the stored flow data from the database. This code is passed to exec() with zero sandboxing, resulting in unauthenticated remote code execution. This is distinct from CVE-2025-3248, which fixed /api/v1/validate/code by adding authentication. The build_public_tmp

    • Auf 1.9.0 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2026-27966

    Kritisch · CVSS 9.8EPSS 35,25%Öffentlicher ExploitKeine Korrektur veröffentlicht

    Langflow has Remote Code Execution in CSV Agent

    Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to version 1.8.0, the CSV Agent node in Langflow hardcodes `allow_dangerous_code=True`, which automatically exposes LangChain’s Python REPL tool (`python_repl_ast`). As a result, an attacker can execute arbitrary Python and OS commands on the server via prompt injection, leading to full Remote Code Execution (RCE). Version 1.8.0 fixes the issue.

    Veröffentlicht Aktualisiert
  13. CVE-2026-0770

    Kritisch · CVSS 9.8EPSS 62,56%Im KEV-KatalogÖffentlicher ExploitKeine Korrektur veröffentlicht

    Langflow exec_globals Inclusion of Functionality from Untrusted Control Sphere Remote Code Execution Vulnerability

    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.

    Veröffentlicht Aktualisiert
  14. CVE-2026-21445

    Hoch · CVSS 8.8EPSS 33,29%Öffentlicher ExploitKorrektur verfügbar

    Langflow Missing Authentication on Critical API Endpoints

    Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to version 1.7.0.dev45, multiple critical API endpoints in Langflow are missing authentication controls. The issue allows any unauthenticated user to access sensitive user conversation data, transaction histories, and perform destructive operations including message deletion. This affects endpoints handling personal data and system operations that should require proper authorization. Version 1.7.0.dev45 contains a patch.

    • Auf 1.7.1 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2025-68478

    Hoch · CVSS 7.1EPSS 5,79%Korrektur verfügbar

    Langflow Vulnerable to External Control of File Name or Path

    Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to version 1.7.0, if an arbitrary path is specified in the request body's `fs_path`, the server serializes the Flow object into JSON and creates/overwrites a file at that path. There is no path restriction, normalization, or allowed directory enforcement, so absolute paths (e.g., /etc/poc.txt) are interpreted as is. Version 1.7.0 fixes the issue.

    • Auf 1.7.0 aktualisieren
    • Auf 1.7.1 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2025-68477

    Hoch · CVSS 7.7EPSS 6,3%Korrektur verfügbar

    Langflow vulnerable to Server-Side Request Forgery

    Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to version 1.7.0, Langflow provides an API Request component that can issue arbitrary HTTP requests within a flow. This component takes a user-supplied URL, performs only normalization and basic format checks, and then sends the request using a server-side httpx client. It does not block private IP ranges (127[.]0[.]0[.]1, the 10/172/192 ranges) or cloud metadata endpoints (169[.]254[.]169[.]254), and it returns the response body as the result. Because the flow execution endpoints (/api/v1/run, /api/v1/run/advanced) can be invoked with just an API key, if an

    • Auf 1.7.1 aktualisieren
    Veröffentlicht Aktualisiert
  17. CVE-2025-34291

    Kritisch · CVSS 9.4EPSS 92,81%Im KEV-KatalogÖffentlicher ExploitKorrektur verfügbar

    Langflow <= 1.6.9 CORS Misconfiguration to Token Hijack & RCE

    Langflow versions up to and including 1.6.9 contain a chained vulnerability that enables account takeover and remote code execution. An overly permissive CORS configuration (allow_origins='*' with allow_credentials=True) combined with a refresh token cookie configured as SameSite=None allows a malicious webpage to perform cross-origin requests that include credentials and successfully call the refresh endpoint. An attacker-controlled origin can therefore obtain fresh access_token / refresh_token pairs for a victim session. Obtained tokens permit access to authenticated endpoints — including built-in code-execution functionality — allowing the

    • Auf 1.7.0 aktualisieren
    Veröffentlicht Aktualisiert
  18. CVE-2025-57760

    Hoch · CVSS 8.8EPSS 0,54%Korrektur verfügbar

    Langflow Vulnerable to Privilege Escalation via CLI Superuser Creation

    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.

    • Auf 1.5.0 aktualisieren
    • Auf 1.5.1 aktualisieren
    Veröffentlicht Aktualisiert
  19. CVE-2025-3248

    Kritisch · CVSS 9.8EPSS 99,99%Im KEV-KatalogÖffentlicher ExploitKorrektur verfügbar

    Langflow < 1.3.0 Unauthenticated RCE via /api/v1/validate/code

    Langflow versions prior to 1.3.0 are susceptible to code injection in the /api/v1/validate/code endpoint. A remote and unauthenticated attacker can send crafted HTTP requests to execute arbitrary code.

    • Auf 1.3.0 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →