CVE-2025-71335: Flowise - Session Invalidation Failure After Password Change
Flowise before 3.0.10 (affected versions 3.0.7 and earlier) fails to invalidate existing sessions and session tokens after a user changes their password. An attacker who already holds an active session, for example via a stolen session token or a device left logged in, remains authenticated as the legitimate user even after the user rotates their credentials, undermining the security purpose of the password change.
Security readout for executives and security teams
Plain-English summary
Flowise may let an old logged-in session stay active after a user changes their password. If someone already stole a session token or has access to a logged-in device, the password change may not remove their access.
Executive priority
Prioritize remediation for exposed or business-critical Flowise deployments. The flaw does not create initial access by itself, but it can preserve unauthorized access after a password reset, weakening incident response and account recovery.
Technical view
CVE-2025-71335 is a CWE-613 session invalidation flaw in Flowise. Sources describe Flowise before 3.0.10, including 3.0.7 and earlier, as affected. Existing sessions and session tokens are not invalidated after password change. CVSS 4.0 score is 8.6 high.
Likely exposure
Exposure is limited to Flowise deployments with authenticated users where an attacker already has an active session, stolen token, or access to a logged-in device. Internet-accessible administrative or sensitive AI workflow environments have higher business risk.
Exploitation context
No source in the bundle states active exploitation, and it is not listed as KEV. Abuse requires an already-valid session or token. The issue undermines password rotation and account recovery by allowing prior sessions to remain authenticated.
Researcher notes
The CVSS vector indicates network attack surface, low complexity, low privileges, no user interaction, and high confidentiality and integrity impact. Availability impact is not indicated. Evidence provided does not include exploit availability or active exploitation.
Mitigation direction
Upgrade Flowise to version 3.0.10 or later, per the affected-version information.
Review vendor advisory for any additional session-management guidance.
Force logout or revoke existing sessions after upgrading, if supported.
Treat suspected stolen session tokens as account compromise events.
Validation and detection
Inventory Flowise deployments and record running versions.
Identify instances running Flowise 3.0.7 or earlier, or otherwise before 3.0.10.
In a controlled test, verify password changes terminate prior sessions.
Review logs for session use continuing after password changes.
Confirm operational procedures include session revocation after credential compromise.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-613: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-613 · source CWE mapping
Insufficient Session Expiration
Insufficient Session Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.