CVE-2025-58434: Flowise Cloud and Local Deployments have Unauthenticated Password Reset Token Disclosure that Leads to Account Takeover
Noroxi assessment
Priority: This week (action score 64/100)
- A ready-made attack module is public (Metasploit, Nuclei); exploiting it takes no special expertise.
- Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 83.8% (FIRST EPSS); higher than 99.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: flowise (npm) 3.0.6.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Don’t wait for the next maintenance window. Upgrade to flowise (npm) 3.0.6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 12, 2025
- Updated
- Sep 30, 2026
- EPSS
- 83.8% · 99th percentile
- CWE
- CWE-306
Report tools
Action score
64
Don’t wait for the next maintenance window.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 25 / 30 · 83.8%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Weaponized exploit exists
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| flowiseai | flowise | cpe:2.3:a:flowiseai:flowise |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
FlowiseAI Flowise
- <= 3.0.5affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- flowiseai flowisebefore 3.0.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | flowise | before 3.0.6 | 3.0.6 |
Same product
flowiseai: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-59528Flowise has Remote Code Execution vulnerability68This week
- CVE-2025-8943Unsupervised OS command execution leads to remote code execution by unauthenticated network attackers61This week
- CVE-2026-41264Flowise: CSV Agent Prompt Injection Remote Code Execution Vulnerability60This week
Published before and after this one in the same product
- ← EarlierCVE-2025-26319Mar 4, 2025 · FlowiseAI Flowise v2.2.6 was discovered to contain an arbitrary file upload vulnerability in /api/v1/attachments.56Plan
- ← EarlierCVE-2025-29189Apr 9, 2025 · Flowise <= 2.2.3 is vulnerable to SQL Injection.30Monitor
- Later →CVE-2025-59434Sep 22, 2025 · Critical Multi-Tenant Variable Disclosure in Flowise Cloud via Custom JavaScript Function39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| npm:flowise | 3.0.6 | Package registry (OSV) |
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
- Exploit-DB entry ×1
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×16
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | 16 repositories | 2026-04-12 → 2026-09-08 |
| Exploit-DB entry | webapps | 2026-05-13 |
| Metasploit module | auxiliary/admin/http/flowise_auth_bypass_cve_2025_58434Flowise Authentication Bypassauxiliary | 2025-09-12 |
| Nuclei detection template | Nuclei template CVE-2025-58434 | — |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Metasploit-1 d
- Published
- First PoC+211 d
- TodayNov 16, 2026+430 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-894329 days apartUnsupervised OS command execution leads to remote code execution by unauthenticated network attackers61This week
- CVE-2026-30824176 days apartFlowise: Missing Authentication on NVIDIA NIM Endpoints41Plan
- CVE-2025-71327286 days apartFlowise - Authentication Bypass via Unprotected Registration Endpoint37Monitor
- CVE-2026-56270285 days apartFlowise - Unauthenticated OAuth Secrets Disclosure via /api/v1/loginmethod Endpoint35Monitor
- CVE-2026-41273223 days apartFlowise: Unauthenticated OAuth 2.0 Access Token Disclosure via Public Chatflow30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2025-6191326 days apartFlowise is vulnerable to arbitrary file read, arbitrary file write43Plan
- CVE-2025-6168724 days apartFlowiseAI/Flosise has File Upload vulnerability39Monitor
- CVE-2025-3426732 days apartFlowise Authenticated Command Execution and Sandbox Bypass via Puppeteer & Playwright Packages35Monitor
- CVE-2025-29189156 days apartFlowise <= 2.2.3 is vulnerable to SQL Injection.30Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-25-0248 · Sep 15, 2025(Flowise Güvenlik Zafiyeti)
Not on record for this CVE: researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-306 · Missing Authentication for Critical FunctionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
A function added for development or support ships to production without authentication. It often relies on the assumption that it is “only reachable from the internal network.”
The bug in code
The whole CWE-306 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
// Added for the support team
app.post("/maintenance/reset", resetDevice);Fixed
if (config.maintenanceEnabled) {
app.post(
"/maintenance/reset",
requireSession, requireRole("admin"), resetDevice
);
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (2)
- Exploit maturitypoc → weaponized
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.