← Back
CVE-2026-55255
CISA KEV
high
CVSS 8.4
[KEV] Vulnerability in langflow (CVE-2026-55255)
Summary
vulnerability in langflow (CVE-2026-55255). Confidential information can be exposed externally. Exploitable via ``get_flow_by_id_or_endpoint_name``. Listed in CISA KEV — actively exploited. Mitigation: upgrade to `1.9.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-55255** has been found in langflow.
Attackers can target a specific entry point like ``get_flow_by_id_or_endpoint_name`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.4/10.
Note: CISA has officially confirmed this is **actively exploited in the wild**. Treat it with elevated urgency.
What to do: upgrade langflow to **1.9.1** or later.
If unsure, ask your IT team or search "langflow CVE-2026-55255" on the vendor's site.
CVE-2026-55255 (langflow) — CWE-639 / CVSS v3 8.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `get_flow_by_id_or_endpoint_name` / `user_id` / `endpoint_name`
Patched: `1.9.1` — apply immediately
Listed in CISA KEV — actively exploited, treat as top priority.
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
**A vulnerability** (CWE-639) exists in langflow. Attackers reach the vulnerable code path via ``get_flow_by_id_or_endpoint_name`` without authentication.
📍 Affected scope
langflow — . Attack surface: `get_flow_by_id_or_endpoint_name` / `user_id` / `endpoint_name`.
🔥 Severity
Severity: High (CVSS 8.4/10). Confidential information can be exposed externally **Listed in CISA KEV** — actively exploited in the wild, treat as top priority.
🔧 How to fix
Update to **1.9.1**.
🛡️ 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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
4Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。Step 3 で兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
6Apply patch patch
Upgrade langflow to 1.9.1ステージング環境で 1.9.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
langflow
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.9.1"}]}]
References
- advisory 134c704f-9b21-4f2e-91b3-4a467353bcc0
- exploit 134c704f-9b21-4f2e-91b3-4a467353bcc0
- patch [email protected]
- patch [email protected]
- web https://github.com/advisories/GHSA-qrpv-q767-xqq2
- web https://nvd.nist.gov/vuln/detail/CVE-2026-55255
- web 134c704f-9b21-4f2e-91b3-4a467353bcc0
- web https://github.com/pypa/advisory-database/tree/main/vulns/langflow/PYSEC-2026-221.yaml