Persistent account access via unrevoked sessions
Published Jun 25, 2026 · Updated Jun 25, 2026
Session invalidation failure in Flowise 3.0.7 and earlier allows remote authenticated users to retain access after password changes. The password-change flow leaves previously issued sessions and session tokens valid instead of revoking them. Exploitation requires an existing session, such as a stolen token or logged-in device, and preserves the account's read and write access.
Summary
What happened
Session invalidation failure in Flowise 3.0.7 and earlier allows remote authenticated users to retain access after password changes. The password-change flow leaves previously issued sessions and session tokens valid instead of revoking them. Exploitation requires an existing session, such as a stolen token or logged-in device, and preserves the account's read and write access.
The record
- CVE
- CVE-2025-71335
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- CWE-613
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.0.10
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Two-browser session persistence reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo