Vulnerability in flowise (CVE-2025-71335)
Summary
Vulnerability in flowise (CVE-2025-71335). Confidential information can be exposed externally. Mitigation: upgrade to 3.0.10 or later.
Original description
The description as published by the source.
Summary
Failure to Invalidate Existing Sessions After Password Change (Persistent Session / Session Invalidity Failure).
Details
After a user changes their password, the application does not invalidate other active sessions or session tokens that were established before the change. An attacker who already has an active session (e.g., via a stolen session token, device left logged in, or other access) continues to be authenticated even after the legitimate user rotates credentials, allowing the attacker to retain access despite the user’s password change.
PoC
Repro steps:
- As logged in user on two browsers (ie. Chrome and Firefox, with incognito/private mode) https://cloud.flowiseai.com/account change password, on the Chrome for example
- Refresh the site on Firefox (second browser) - notice that still logged in (despite credentials were changed)
POC:
Steps described above (in Repro steps) completed successfully.
Impact
Persistent unauthorized access despite credential rotation - undermines the primary purpose of password changes as a remediation step.
Enables attackers with an active session (remote or physical access to a device) to continue acting as the user (confidentiality and integrity impact).
If session tokens are not bound to the credential state, forced password changes won’t terminate attacker sessions.
Resources
OWASP Session Management Cheat Sheet
CWE-613: Insufficient Session Expiration
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-2025-71335 has been found in flowise.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade flowise to 3.0.10 or later.
If unsure, ask your IT team or search "flowise CVE-2025-71335" on the vendor's site.
CVE-2025-71335 (flowise) — CWE-613 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 3.0.10 — 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 flowise.
Check the vendor advisory for the affected versions of flowise.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 3.0.10.
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 'flowise' . 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 'flowise' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
flowiseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade flowise to 3.0.10ステージング環境で 3.0.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory disclosure@vulncheck.com
- exploit disclosure@vulncheck.com
- package github.com
- web nvd.nist.gov
- web github.com
- web github.com