Which versions of Flowise are affected by CVE-2025-71335?

Flowise versions 3.0.7 and earlier contain a session persistence vulnerability that allows attackers with stolen authentication tokens to retain account access even after victims change their…. A patch is available.

How to fix or mitigate CVE-2025-71335?

Within 24 hours: Inventory all Flowise deployments and identify systems running versions 3.0.7 or earlier. Within 7 days: Upgrade all affected instances to Flowise 3.0.10 and force immediate re-authentication of all users to invalidate existing sessions. Within 30 days: Review pre-patch access logs for unauthorized account activity and notify any users with confirmed unauthorized access.

Flowise CVE-2025-71335

Q: What is the CVSS score of CVE-2025-71335?

CVE-2025-71335 has a CVSS 4.0 base score of 8.6 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

EUVD-2025-210341 HIGH

Insufficient Session Expiration (CWE-613)

2026-06-25 VulnCheck

GHSA-289x-5mj7-xhg5

Information Disclosure Flowise

8.6

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

8.6 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

8.1 HIGH

Network-reachable with low complexity; PR:L because the attacker must already hold a valid session; high confidentiality and integrity over the account, no availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jun 25, 2026 - 23:04 EUVD

Source Code Evidence Fetched

Jun 25, 2026 - 22:34 vuln.today

Analysis Generated

Jun 25, 2026 - 22:34 vuln.today

DescriptionCVE.org

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.

AnalysisAI

Persistent session hijacking in Flowise 3.0.7 and earlier (fixed in 3.0.10) lets an attacker retain authenticated access to a victim's account even after the victim changes their password, because the application never invalidates pre-existing sessions or session tokens on credential rotation (CWE-613). Anyone holding a stolen token or a device left logged in keeps full access, defeating the primary remediation users rely on after a suspected compromise. A working proof-of-concept is published in the vendor's GHSA advisory; publicly available exploit code exists, but there is no public exploit identified as actively exploited in the wild and it is not on the CISA KEV list.

Technical ContextAI

Flowise is an open-source, low-code platform for building LLM/agent workflows, distributed via the npm package 'flowise' (CPE cpe:2.3:a:flowise:flowise) and offered as a cloud service at cloud.flowiseai.com. The flaw is an instance of CWE-613 (Insufficient Session Expiration): the session management layer issues session tokens that are not bound to the user's credential state, so the password-change routine updates the stored credential without iterating and revoking outstanding sessions. Because there is no server-side linkage between an active session and the current password hash, token validity persists independently of credential changes - the application trusts a previously issued token indefinitely until its own (unchanged) expiry. This is the classic gap the OWASP Session Management Cheat Sheet warns about: security-sensitive events (password change, reset, MFA enrollment) must trigger global session invalidation.

RemediationAI

Vendor-released patch: upgrade Flowise to version 3.0.10 or later (fix delivered via https://github.com/FlowiseAI/Flowise/pull/5294), which is the definitive fix and should be applied per the GHSA advisory at https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-x7rp-qj2h-ghgw. Until the upgrade is deployed, compensating controls include forcing all users to re-authenticate by invalidating the server-side session store (for example, rotating the session signing secret / JWT secret so all existing tokens become invalid - side effect: every active user is logged out and must sign in again), and shortening session/token lifetime to reduce the window in which a stolen token remains usable (side effect: more frequent logins for legitimate users). For high-value or internet-exposed instances, restrict network access to the Flowise UI/API to trusted networks or behind a VPN/SSO reverse proxy that can enforce its own session revocation, so an upstream identity layer can terminate sessions on password change even though Flowise itself cannot. After any suspected credential compromise on an unpatched instance, treat a password change as insufficient and additionally rotate the session secret rather than relying on the password change alone.