Vulnerability in langflow (CVE-2026-55423)
Summary
Vulnerability in langflow (CVE-2026-55423). Confidential information can be exposed externally. Exploitable via access_token_lf. Mitigation: upgrade to 1.7.0 or later.
Original description
The description as published by the source.
Summary
The logout button does not clear the session. The previous user stays logged in unless another user explicitly logs in.
Details
Not in auto login mode. Hosted on localhost. access_token_lf remains present in both Local Storage and Cookies. refresh_token_lf remains present in Cookies.
Root cause: the /logout endpoint deleted the authentication cookies without matching the original httponly/samesite/secure/domain parameters, so the browser kept them; additionally the frontend did not clear the auth cookies on logout.
LANGFLOW_AUTO_LOGIN: "False"
LANGFLOW_SUPERUSER:
LANGFLOW_SUPERUSER_PASSWORD:
LANGFLOW_SECRET_KEY:
LANGFLOW_NEW_USER_IS_ACTIVE: "False"
LANGFLOW_ENABLE_SUPERUSER_CLI: "False"
PoC
Click Logout. Hit refresh to return to previous screen.
Impact
Users on shared computers may falsely believe they have terminated their session.
Patches
Fixed in 1.7.0 (PRs #10527 and #10528). The logout endpoint now deletes the auth cookies using the same parameters they were created with, and the frontend clears the auth cookies on logout. Upgrade to 1.7.0 or later.
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-55423 has been found in langflow.
Attackers can target a specific entry point like access_token_lf 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.7.0 or later.
If unsure, ask your IT team or search "langflow CVE-2026-55423" on the vendor's site.
CVE-2026-55423 (langflow) — CWE-613 / CVSS v3 6.1
Attack vector: physical / unauthenticated / no user interaction
Attack surface: access_token_lf / refresh_token_lf / httponly / samesite
Patched: 1.7.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-613) exists in langflow. Attackers reach the vulnerable code path via access_token_lf without authentication.
Check the vendor advisory for the affected versions of langflow. Attack surface: access_token_lf / refresh_token_lf / httponly / samesite.
Severity: Medium (CVSS 6.1/10). Confidential information can be exposed externally.
Update to 1.7.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.7.0ステージング環境で 1.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com