Home

Description

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.

PUBLISHED Reserved 2026-06-20 | Published 2026-06-25 | Updated 2026-06-26 | Assigner VulnCheck




HIGH: 8.6CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
HIGH: 8.1CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Problem types

Insufficient Session Expiration

Product status

Default status
unaffected

Any version before 3.0.10
affected

3.0.10 (semver)
unaffected

Credits

mbiesiad reporter

References

github.com/...lowise/security/advisories/GHSA-x7rp-qj2h-ghgw (GitHub Security Advisory (GHSA-x7rp-qj2h-ghgw)) vendor-advisory

www.vulncheck.com/...alidation-failure-after-password-change (VulnCheck Advisory: Flowise - Session Invalidation Failure After Password Change) third-party-advisory

cve.org (CVE-2025-71335)

nvd.nist.gov (CVE-2025-71335)

Download JSON