Vulnerability in langflow (CVE-2026-48520)
Summary
Vulnerability in langflow (CVE-2026-48520). Confidential information can be exposed externally. Exploitable via files. Mitigation: upgrade to 1.10.0 or later.
Original description
The description as published by the source.
Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to 1.10.0, the "Shareable Playground" (or "Public Flows" in code) contains a potential arbitrary file-read vulnerability, depending on the exact flow configuration used. By making a flow public, public execution of the flow is allowed. The execution request can contain a list of files that gets read by Langflow and fed into the LLM. The files path can be any path supported by the storage - it can be either a local file or S3 path if supported by the local configuration This vulnerability is fixed in 1.10.0.
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-48520 has been found in langflow.
Attackers can target a specific entry point like files over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.1/10.
What to do: upgrade langflow to 1.10.0 or later.
If unsure, ask your IT team or search "langflow CVE-2026-48520" on the vendor's site.
CVE-2026-48520 (langflow) — CWE-73 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: files / LCModelComponent._get_chat_result / to_lc_message
Patched: 1.10.0 — 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.
A vulnerability (CWE-73) exists in langflow. Attackers reach the vulnerable code path via files without authentication.
Check the vendor advisory for the affected versions of langflow. Attack surface: files / LCModelComponent._get_chat_result / to_lc_message.
Severity: Medium (CVSS 6.1/10). Confidential information can be exposed externally.
Update to 1.10.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
grep -r 'langflow' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
langflowを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade langflow to 1.10.0ステージング環境で 1.10.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com