CVE-2025-71335
Flowiseai Flowise vulnerability
- Published25 Jun 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-71335 being actively exploited?
CVE-2025-71335 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.38%.
How severe is CVE-2025-71335?
CVE-2025-71335 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.38% probability of exploitation.
Which products are affected by CVE-2025-71335?
Affected products include Flowiseai Flowise.
How do I fix CVE-2025-71335?
Upgrade affected software to a fixed version, for example Flowiseai Flowise 3.0.10 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-71335 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.