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
Trending — 3 sources updated this week
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.0%
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 39× in last 7d / 66× 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-07 06:26 UTCEG score recompute
  2. 2026-07-07 06:26 UTCGHSA enrichment
  3. 2026-07-06 19:10 UTCEG score recompute
  4. 2026-07-06 19:10 UTCGHSA enrichment
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 07:54 UTCEG score recompute
  7. 2026-07-06 07:53 UTCGHSA enrichment
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 20:35 UTCEG score recompute
  10. 2026-07-05 20:34 UTCGHSA enrichment
  11. 2026-07-05 09:19 UTCEG score recompute
  12. 2026-07-05 09:18 UTCGHSA enrichment
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 22:02 UTCEG score recompute
  16. 2026-07-04 22:02 UTCGHSA enrichment
  17. 2026-07-04 10:45 UTCEG score recompute
  18. 2026-07-04 10:45 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-03 23:26 UTCEG score recompute
  22. 2026-07-03 23:26 UTCGHSA enrichment
  23. 2026-07-03 12:11 UTCEG score recompute
  24. 2026-07-03 12:10 UTCGHSA enrichment
  25. 2026-07-03 00:53 UTCEG score recompute
Show 41 more
  1. 2026-07-03 00:53 UTCGHSA enrichment
  2. 2026-07-02 13:37 UTCEG score recompute
  3. 2026-07-02 13:37 UTCGHSA enrichment
  4. 2026-07-02 02:21 UTCEG score recompute
  5. 2026-07-02 02:21 UTCGHSA enrichment
  6. 2026-07-01 15:06 UTCEPSS rescore
  7. 2026-07-01 15:05 UTCEG score recompute
  8. 2026-07-01 15:05 UTCGHSA enrichment
  9. 2026-07-01 03:48 UTCEG score recompute
  10. 2026-07-01 03:48 UTCGHSA enrichment
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 16:32 UTCEG score recompute
  14. 2026-06-30 16:32 UTCGHSA enrichment
  15. 2026-06-30 05:16 UTCEG score recompute
  16. 2026-06-30 05:16 UTCGHSA enrichment
  17. 2026-06-29 18:00 UTCEG score recompute
  18. 2026-06-29 18:00 UTCGHSA enrichment
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-29 06:43 UTCEG score recompute
  22. 2026-06-29 06:43 UTCGHSA enrichment
  23. 2026-06-28 19:27 UTCEG score recompute
  24. 2026-06-28 19:27 UTCGHSA enrichment
  25. 2026-06-28 14:07 UTCEPSS rescore
  26. 2026-06-28 14:07 UTCEPSS rescore
  27. 2026-06-28 08:11 UTCEG score recompute
  28. 2026-06-28 08:11 UTCGHSA enrichment
  29. 2026-06-28 04:56 UTCEPSS rescore
  30. 2026-06-28 04:56 UTCEPSS rescore
  31. 2026-06-27 20:55 UTCEG score recompute
  32. 2026-06-27 20:55 UTCGHSA enrichment
  33. 2026-06-27 09:39 UTCEG score recompute
  34. 2026-06-27 09:39 UTCGHSA enrichment
  35. 2026-06-27 03:08 UTCEPSS rescore
  36. 2026-06-26 22:22 UTCEG score recompute
  37. 2026-06-26 22:22 UTCGHSA enrichment
  38. 2026-06-26 11:07 UTCEG score recompute
  39. 2026-06-26 11:07 UTCGHSA enrichment
  40. 2026-06-25 23:51 UTCEG score recompute
  41. 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.0% 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

Explore the affected products and dependency analysis for 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