Vulnerability in langflow-base (CVE-2026-21445)
Summary
Vulnerability in langflow-base (CVE-2026-21445). Risk of unauthorized operations or information disclosure. Exploitable via get_current_active_user. Mitigation: upgrade to 0.7.1 or later.
Original description
The description as published by the source.
Summary
Multiple critical API endpoints in Langflow are missing authentication controls, allowing 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.
Details
The vulnerability exists in three API endpoints within src/backend/base/langflow/api/v1/monitor.py that are missing the required dependencies=[Depends(get_current_active_user)] authentication dependency:
Affected Endpoints:
-
GET
/api/v1/monitor/messages(Line 61)@router.get("/messages") # ❌ Missing authentication async def get_messages( session: DbSession, flow_id: Annotated[UUID | None, Query()] = None, session_id: Annotated[str | None, Query()] = None, # ... other parameters ) -> list[MessageResponse]: -
GET
/api/v1/monitor/transactions(Line 183)@router.get("/transactions") # ❌ Missing authentication async def get_transactions( flow_id: Annotated[UUID, Query()], session: DbSession, params: Annotated[Params | None, Depends(custom_params)], ) -> Page[TransactionTable]: -
DELETE
/api/v1/monitor/messages/session/{session_id}(Line 165)@router.delete("/messages/session/{session_id}", status_code=204) # ❌ Missing authentication async def de…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-21445 has been found in langflow-base.
Attackers can target a specific entry point like get_current_active_user over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade langflow-base to 0.7.1 or later.
If unsure, ask your IT team or search "langflow-base CVE-2026-21445" on the vendor's site.
CVE-2026-21445 (langflow-base) — CWE-306
Attack surface: get_current_active_user
Patched: 0.7.1 — 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-306) exists in langflow-base. Attackers reach the vulnerable code path via get_current_active_user.
Check the vendor advisory for the affected versions of langflow-base. Attack surface: get_current_active_user.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.7.1.
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-base' . 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-base' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
langflow-baseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade langflow-base to 0.7.1ステージング環境で 0.7.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com