Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55447 critical CVSS 9.6

Information Disclosure in langflow (CVE-2026-55447)

Summary

Vulnerability in langflow (CVE-2026-55447). Successful exploitation can lead to full system takeover. Exploitable via BaseFileComponent. Mitigation: upgrade to 1.9.2 or later.

Original description

The description as published by the source.

Summary

All components based on BaseFileComponent are vulnerable to the following vulnerability:

  1. Docling (DoclingInlineComponent)
  2. Docling Serve (DoclingRemoteComponent)
  3. Read File (FileComponent)
  4. NVIDIA Retriever Extraction (NvidiaIngestComponent)
  5. Video File (VideoFileComponent)
  6. Unstructured API (UnstructuredComponent)

For clarity, from now on I'll only refer to Read File component.

The Read File node processes user-controlled files.
Example scenario is a RAG chatbot - a system that allows users of an organization to ask questions about documents saved in the organizations.

By controlling a files that are digested into the RAG, an attacker can direct the node to read any file on the file-system by absolute path.

Using this vulnerability an attacker can acheive RCE:

  1. Upload a file that directs the node to read Langflow's secret_key file containing the JWT token secret.
  2. This would allow the attacker then to simply task the Chatbot for the JWT secret.
  3. Using this secret, the attacker then crafts a JWT token for any user-id, bypassing authentication.
  4. Code execution is then trivial - simply create a new flow with "Python Interpreter" node, fill it with arbitrary Python code and execute it.

Tested on commit 2d67402b1dbaefcbce85a244d4a6cd5e4bda1cfe

Details

The vulnerability is in:
langflow/src/lfx/src/lfx/base/data/base_file.py
Specifically in _unpack_bundle. This function extracts tar files, which can contain a symlin…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-55447 has been found in langflow.
Attackers can target a specific entry point like BaseFileComponent over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.6/10.
What to do: upgrade langflow to 1.9.2 or later.
If unsure, ask your IT team or search "langflow CVE-2026-55447" on the vendor's site.

CVE-2026-55447 (langflow) — CWE-200 / CVSS v3 9.6
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: BaseFileComponent / DoclingInlineComponent / DoclingRemoteComponent / FileComponent
Patched: 1.9.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in langflow. Attackers reach the vulnerable code path via BaseFileComponent without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of langflow. Attack surface: BaseFileComponent / DoclingInlineComponent / DoclingRemoteComponent / FileComponent.

🔥 Severity

Severity: Critical (CVSS 9.6/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.9.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'langflow' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'langflow' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で langflow を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade langflow to 1.9.2

    ステージング環境で 1.9.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip langflow
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.9.2"}]}]
PyPI langflow
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.9.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details