CVE-2025-71335

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
8.1
EG Score
8.1(high)
EPSS
18.3%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 1, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Flowise - Session Invalidation Failure After Password Change | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-session-invalidation-failure-after-password-change
github Patch Available🟡 PoC Available

Failure to Invalidate Existing Sessions After Password Change · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-x7rp-qj2h-ghgw

Vendor Advisories for CVE-2025-71335(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
flowise—3.0.10—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 86× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:30 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 02:28 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-17 04:54 UTCGHSA enrichment
  11. 2026-07-16 17:37 UTCGHSA enrichment
  12. 2026-07-16 17:02 UTCEPSS rescore
  13. 2026-07-16 17:02 UTCEPSS rescore
  14. 2026-07-16 05:16 UTCGHSA enrichment
  15. 2026-07-15 18:00 UTCGHSA enrichment
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 06:44 UTCGHSA enrichment
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-15 01:59 UTCEPSS rescore
  21. 2026-07-14 19:27 UTCGHSA enrichment
  22. 2026-07-14 08:11 UTCGHSA enrichment
  23. 2026-07-13 20:29 UTCGHSA enrichment
  24. 2026-07-13 09:13 UTCGHSA enrichment
  25. 2026-07-13 06:12 UTCEPSS rescore
Show 61 more
  1. 2026-07-12 21:55 UTCGHSA enrichment
  2. 2026-07-12 10:39 UTCGHSA enrichment
  3. 2026-07-12 05:46 UTCEPSS rescore
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 23:22 UTCGHSA enrichment
  6. 2026-07-11 12:05 UTCGHSA enrichment
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-11 00:49 UTCGHSA enrichment
  10. 2026-07-10 13:33 UTCGHSA enrichment
  11. 2026-07-10 02:16 UTCGHSA enrichment
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-09 14:59 UTCGHSA enrichment
  14. 2026-07-09 03:42 UTCGHSA enrichment
  15. 2026-07-08 16:25 UTCGHSA enrichment
  16. 2026-07-08 15:15 UTCEPSS rescore
  17. 2026-07-08 05:09 UTCGHSA enrichment
  18. 2026-07-07 17:50 UTCGHSA enrichment
  19. 2026-07-07 13:46 UTCEPSS rescore
  20. 2026-07-07 06:26 UTCGHSA enrichment
  21. 2026-07-06 19:10 UTCGHSA enrichment
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-06 07:53 UTCGHSA enrichment
  24. 2026-07-06 02:23 UTCEPSS rescore
  25. 2026-07-05 20:34 UTCGHSA enrichment
  26. 2026-07-05 09:18 UTCGHSA enrichment
  27. 2026-07-05 02:30 UTCEPSS rescore
  28. 2026-07-05 02:30 UTCEPSS rescore
  29. 2026-07-04 22:02 UTCGHSA enrichment
  30. 2026-07-04 10:45 UTCGHSA enrichment
  31. 2026-07-04 06:31 UTCEPSS rescore
  32. 2026-07-04 06:31 UTCEPSS rescore
  33. 2026-07-03 23:26 UTCGHSA enrichment
  34. 2026-07-03 12:10 UTCGHSA enrichment
  35. 2026-07-03 00:53 UTCGHSA enrichment
  36. 2026-07-02 13:37 UTCGHSA enrichment
  37. 2026-07-02 02:21 UTCGHSA enrichment
  38. 2026-07-01 15:06 UTCEPSS rescore
  39. 2026-07-01 15:05 UTCGHSA enrichment
  40. 2026-07-01 03:48 UTCGHSA enrichment
  41. 2026-06-30 23:22 UTCEPSS rescore
  42. 2026-06-30 23:22 UTCEPSS rescore
  43. 2026-06-30 16:32 UTCGHSA enrichment
  44. 2026-06-30 05:16 UTCGHSA enrichment
  45. 2026-06-29 18:00 UTCGHSA enrichment
  46. 2026-06-29 14:06 UTCEPSS rescore
  47. 2026-06-29 14:06 UTCEPSS rescore
  48. 2026-06-29 06:43 UTCGHSA enrichment
  49. 2026-06-28 19:27 UTCGHSA enrichment
  50. 2026-06-28 14:07 UTCEPSS rescore
  51. 2026-06-28 14:07 UTCEPSS rescore
  52. 2026-06-28 08:11 UTCGHSA enrichment
  53. 2026-06-28 04:56 UTCEPSS rescore
  54. 2026-06-28 04:56 UTCEPSS rescore
  55. 2026-06-27 20:55 UTCGHSA enrichment
  56. 2026-06-27 09:39 UTCGHSA enrichment
  57. 2026-06-27 03:08 UTCEPSS rescore
  58. 2026-06-26 22:22 UTCGHSA enrichment
  59. 2026-06-26 11:07 UTCGHSA enrichment
  60. 2026-06-25 23:51 UTCEG score recompute
  61. 2026-06-25 23:50 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-71335?
CVE-2025-71335 is a high vulnerability published on June 25, 2026. 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…
When was CVE-2025-71335 disclosed?
CVE-2025-71335 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-71335 actively exploited?
CVE-2025-71335 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-71335?
CVE-2025-71335 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2025-71335?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71335, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71335

Explore →

Is Your Infrastructure Affected by CVE-2025-71335?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs