CVE-2025-71335

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM 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.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 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(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
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 23× in last 7d / 108× 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.

Showing the most recent 100 of 206 total refreshes for this CVE.

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

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 0% probability of exploitation in the next 30 days, which ranks it in the top 69.3% of all scored CVEs.
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