Flowise fails to invalidate sessions after password changes
Flowise
Flowise failed to invalidate active session tokens after a user changed their password. This could allow an attacker with a prior session token to maintain unauthorized access.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- fix status
- Fix status unknown
- first report
- 14 Nov 2025
- last update
- 14 Nov 2025
Timeline · 1
Sources · 1
Advisories and databases
- 2025-11-14GHSA-x7rp-qj2h-ghgw: Flowise Fails to Invalidate Existing Sessions After Password ChangesGitHub Advisory Database · github.com/advisories/GHSA-x7rp-qj2h-ghgw
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- dates
- happened 14 Nov 2025 · first reported 14 Nov 2025
- origin
- GitHub Advisory DatabaseVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 07:00Z · updated 2026-10-18 10:14Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# Flowise fails to invalidate sessions after password changes https://gcdradar.vercel.app/incidents/ghsa-x7rp-qj2h-ghgw-flowise-fails-to-invalidate-sessions-aft · AIR-2025-0371 · closed 2025-11-14 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2025-11-14 - AI role: Attack on AI - Products: Flowise ## Summary Flowise failed to invalidate active session tokens after a user changed their password. This could allow an attacker with a prior session token to maintain unauthorized access. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2025-11-14: GHSA-x7rp-qj2h-ghgw: Flowise Fails to Invalidate Existing Sessions After Password Changes (https://github.com/advisories/GHSA-x7rp-qj2h-ghgw) ## Sources - 2025-11-14 GitHub Advisory Database: GHSA-x7rp-qj2h-ghgw: Flowise Fails to Invalidate Existing Sessions After Password Changes https://github.com/advisories/GHSA-x7rp-qj2h-ghgw Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closedFlowise Flowise authentication bypass using unprotected registration endpoint
Patch now · Disclosed · since 17 Nov 2025
AI - closed5.3Flowise CVE-2026-8027: Authorization bypass in FlowiseAI Flowise user controller handler
Patch now · Disclosed · since 6 May 2026 · CVE-2026-8027
AI - closed3.7Flowise CVE-2026-8028: Information disclosure vulnerability in FlowiseAI Flowise
Patch now · Disclosed · since 6 May 2026 · CVE-2026-8028
AI - closed6.3Flowise Flowise API response handler exposes bcrypt password hashes
Patch now · Disclosed · since 6 May 2026 · CVE-2026-8026
AI - closed7.5Flowise CVE-2026-41275: Cleartext password reset link in Flowise
Patch now · Disclosed · since 23 Apr 2026 · CVE-2026-41275
AI - closed9.8Flowise CVE-2026-41264: Flowise CSV Agent Prompt Injection RCE
Patch now · Disclosed · since 21 Apr 2026 · updated 23 Apr 2026 · CVE-2026-41264
AI