CVE-2025-58434

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 47.3%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 47%CVSS: 9.8Exploit: NoneExposed: 0

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

Flowise is a drag & drop user interface to build a customized large language model flow. In version 3.0.5 and earlier, the forgot-password endpoint in Flowise returns sensitive information including a valid password reset tempToken without authentication or verification. This enables any attacker to generate a reset token for arbitrary users and directly reset their password, leading to a complete account takeover (ATO). This vulnerability applies to both the cloud service (cloud.flowiseai.com) and self-hosted/local Flowise deployments that expose the same API. Commit 9e178d68873eb876073846433a596590d3d9c863 in version 3.0.6 secures password reset endpoints. Several recommended remediation steps are available. Do not return reset tokens or sensitive account details in API responses. Tokens must only be delivered securely via the registered email channel. Ensure forgot-password responds with a generic success message regardless of input, to avoid user enumeration. Require strong validation of the tempToken (e.g., single-use, short expiry, tied to request origin, validated against email delivery). Apply the same fixes to both cloud and self-hosted/local deployments. Log and monitor password reset requests for suspicious activity. Consider multi-factor verification for sensitive accounts.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
78(Attend)
EG Risk 78/100SSVC: Attend

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
Severity98% × 45%
Exploitation47% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
98.7%
KEV
Not listed

Published

September 12, 2025

Last Modified

September 20, 2025

Advisory Details (2)

Auto-updated Jun 13, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Critical: Unauthenticated Password Reset Token Disclosure Leading to Account Takeover in Flowise Cloud and Local Deployments · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-wgpv-6j63-x5ph
github_commit Patch Available

commit 9e178d68873e (FlowiseAI/Flowise)

Patch available: FlowiseAI/Flowise [email protected] (contains commit 9e178d68873e)

https://github.com/FlowiseAI/Flowise/commit/9e178d68873eb876073846433a596590d3d9c863

Affected Packages

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Publicly available exploits

(7 references)

Working exploit code is in the public domain (5 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-52557
    First seen May 13, 2026

    Flowise < 3.0.5 - Missing Authentication for Critical Function

    Open source ↗
  • GitHub PoCkarimelsheikh1/HTB-Silentium-Writeup
    First seen Apr 22, 2026

    Hack The Box - Silentium machine writeup | CVE-2025-58434, CVE-2025-59528, CVE-2025-8110

    Open source ↗
  • GitHub PoCkartik2005221/CVE-2025-58434-AND-59528-POC
    First seen Apr 13, 2026

    Combined PoC for CVE-2025-28434 and CVE-2025-59528

    Open source ↗
  • GitHub PoCTYehan/CVE-2025-58434-59528
    First seen Apr 12, 2026

    CVE-2025-58434 and CVE-2025-59528 chain POC - FlowiseAI Remote Code Execution

    Open source ↗
  • GitHub PoCAzureADTrent/CVE-2025-58434-59528
    First seen Apr 12, 2026

    CVE-2025-58434 and CVE-2025-59528 chain POC

    Open source ↗
  • GitHub PoCjwsly12/CVE-2025-58434-59528-htb-ctf
    First seen Apr 12, 2026

    Exploitation Silentium HTB-CTF

    Open source ↗
  • Nucleihttp/cves/2025/CVE-2025-58434.yaml
    First seen Jan 1, 2025

    Flowise <= 3.0.5 - Account Takeover

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-58434?
CVE-2025-58434 is a critical vulnerability published on September 12, 2025. Flowise is a drag & drop user interface to build a customized large language model flow. In version 3.0.5 and earlier, the forgot-password endpoint in Flowise returns sensitive information including a valid password reset tempToken without authentication or verification. This enables any attacker…
When was CVE-2025-58434 disclosed?
CVE-2025-58434 was first published in the National Vulnerability Database on September 12, 2025, with the most recent update on September 20, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-58434 actively exploited?
CVE-2025-58434 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-58434?
CVE-2025-58434 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-58434?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-58434, 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-58434

Explore →

Is Your Infrastructure Affected by CVE-2025-58434?

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

Start Free Scan →Browse All CVEs