Unauthenticated account creation via reusable registration endpoint
Published Jun 25, 2026 · Updated Jun 25, 2026
Authentication bypass in Flowise 3.0.1 allows remote attackers to create accounts and gain authenticated API access without credentials. The /api/v1/account/register handler remains callable after initial organization setup and accepts repeated unauthenticated user-creation requests. A network-reachable on-premise deployment is sufficient; the resulting account receives access across the Flowise API.
Summary
What happened
Authentication bypass in Flowise 3.0.1 allows remote attackers to create accounts and gain authenticated API access without credentials. The /api/v1/account/register handler remains callable after initial organization setup and accepts repeated unauthenticated user-creation requests. A network-reachable on-premise deployment is sufficient; the resulting account receives access across the Flowise API.
The record
- CVE
- CVE-2025-71327
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- CWE-306, T1136
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Flowise reusable registration request proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo