All vulnerabilities
CVE-2025-58434GHSA-wgpv-6j63-x5ph

Flowise Cloud and Local Deployments have Unauthenticated Password Reset Token Disclosure that Leads to Account Takeover

FlowiseAI FlowisenpmLibraries & packages
CVSS
9.8Critical
ExploitationPublic exploit codeAuxiliary module, 12 Sep 2025 and 1 more. Not in the KEV catalogMetasploit
Exploit odds (EPSS)50.5%Chance of exploitation activity in the next 30 days, higher than 98% of CVEs. Scored 28 Oct 2026FIRST EPSS
Fixed in3.0.6Fixed versionOSV
Published12 Sep 2025Updated 15 Sep 2025CVE List

What fixes it

  • 3.0.6flowise, npmOSVnpm install flowise@3.0.6

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Timeline

  1. 12 Sep 2025Exploit code publicMetasploit
  2. 12 Sep 2025, 17:37 UTCPublishedCVE List

Public exploit code and templates 3

  • Auxiliary moduleFlowise Authentication Bypass 12 Sep 2025Metasploit
  • Webapps exploitFlowise < 3.0.5 - Missing Authentication for Critical Function 13 May 2026Exploit-DB
  • Scanner templateFlowise <= 3.0.5 - Account TakeoverNuclei

Listed so defenders can prioritize. Threatline links to the source and does not host exploit code.

Description

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.

Text from CVE List

Affected versions 2

  • Flowiseaffected: <= 3.0.5CVE List
  • flowise, npmfrom first release, fixed in 3.0.6OSV

References 2