← Back
CVE-2026-33484
Vulnerability in langflow (CVE-2026-33484)
Summary
vulnerability in langflow (CVE-2026-33484). Confidential information can be exposed externally. Exploitable via ``download_image``. Mitigation: upgrade to `1.9.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-33484** has been found in langflow.
Attackers can target a specific entry point like ``download_image`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade langflow to **1.9.0** or later.
If unsure, ask your IT team or search "langflow CVE-2026-33484" on the vendor's site.
CVE-2026-33484 (langflow) — CWE-284 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `download_image` / `flow_id` / `CurrentActiveUser` / `download_file`
Patched: `1.9.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.
❓ What is the problem
**A vulnerability** (CWE-284) exists in langflow. Attackers reach the vulnerable code path via ``download_image`` without authentication.
📍 Affected scope
langflow — . Attack surface: `download_image` / `flow_id` / `CurrentActiveUser` / `download_file`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **1.9.0**.
🛡️ 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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade langflow to 1.9.0ステージング環境で 1.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
langflow
[{"type":"ECOSYSTEM","events":[{"introduced":"1.0.0"},{"fixed":"1.9.0"}]}]
pip
langflow
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.9.0"}]}]
References
- advisory https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33484.json
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-33484
- package https://github.com/langflow-ai/langflow
- web https://github.com/langflow-ai/langflow/security/advisories/GHSA-7grx-3xcx-2xv5
- web https://github.com/pypa/advisory-database/tree/main/vulns/langflow/PYSEC-2026-80.yaml
- web https://github.com/advisories/GHSA-7grx-3xcx-2xv5